The T-code of creating dunning procedure

Could anyone please tell me the T-code of creating the dunning procedure.Thanks in advance

CONFIGURATION PATH:
Financial Accounting -> Account Receivable and Accounts Payable -> Business Transactions -> Dunning -> Dunning Procedure -> Define Dunning Procedures OR Transaction Path:
Accounting/Financial Accounting/Accounts Payable/Periodic Processing/Dunning/Environment/Change
Configuration
TRANSACTION CODE: FBMP
Basically there are three steps in this transaction:
1) Maintain dunning procedure
2) Maintain dunning levels
3) Maintain dunning texts
transaction from SAP:
- Before defining several dunning procedures and forms, you should check whether you can fulfill
all your requirements using one dunning procedure and one form.
- You should select Always dunn. notice? for
the last dunning level so that items at this level are not skipped.
- You can store the header and footer texts separately
for your dunning notices. If your letter paper already contains these specifications, you can remove the windows for these
texts in the form you define using SAPscript.
Regards,
Satish Muvva.

Similar Messages

What is the T-Code for creating Cost center - profit center standard hierar

Hi,
What is the T-Code for creating Cost center - profit center standard hierarchy.Please provide me the T-codes.
Thanks

Hi Supriya,
Create / Change Cost Center Standard Hierarchy - OKEON
Display Cost Center Standard Hierarchy - OKENN
Create Profit Center Standard Hierarchy - KCH1
Change Profit Center Standard Hierarchy - KCH5N
Display Profit Center Standard Hierarchy - KCH6N
Srikanth Munnaluri

What is the function code of create new session?

what is the function code of create new session?
thanks...

Hi
Please put a "/n" (to open a new session after killing the current session)
or "/o" (to open a new session without killing the current session)
or "/i" (to end the current session) before the below T Codes as per your requirement...
For more Tcodes check the following
=>smartforms - Smartforms (SAP Form Builder to Create and Adjust Forms)
=>cmod - Enhancements, User Exits (Project Tool to coordinate changes into projects for the purpose of activating all user exits for a particular project)
=>sale - ALE Customizing
=>bale - Distribution Administration (ALE)
=>wedi - IDOC Type and EDI Basis
=>shdb - BDC (Transaction Recorder)
=>lsmw - LSMW
=>bapi - BAPI
=>spau - Display Modified DE Objects
=>spdd - Display Modified DDIC Objects
=>sara - central idoc archiving
=>stms - Transport Management System
=>wedi - IDOC Type and EDI Basis (IDOC Configuration)
=>bd21 - Analyze change pointers - create IDOC from change pointer
=>bd10 - Send Material Master
=>bd12 - Send Customer Master
=>bd14 - Send Vendor Master
=>bd50 - Activate Change Pointer for Message Type
=>bd55 - Conversion rule user exit (Link conversion rule user exit to the different system \ partner combinations)
=>bd54 - Maintain Logical Systems
=>bd71 - Distribute Customer Model
=>bd87 - Process Inbound IDOCs
=>bd88 - Process Outbound IDOCs
=>bdm2 - Cross-system IDOC Reporting
=>bdm7 - ALE Audit - statistical analyses
=>bdm8 - ALE Audit - sending confirmations
=>bd61 - Activate Change Pointer generally
=>bmv0 - Direct Input Data Transfer Administration
=>rz04 - Operation Mode
=>rz12 - RFC Server Group Maintenance
=>sar3 - Archiving object customizing
=>s001 - SAPoffice Inbox
=>s010 - Standards Texts (SAP Script)
=>se01 - Transport Organizer (Extended View - Performing and managing the transport of development object across different systems)
=>se09 - Transport (Workbench) Organizer (Controlling and keeping track of Development work and Development Objects)
=>se24 - Class Builder (BAPI)
=>se30 - Runtime Analysis
=>se36 - LDB
=>se37 - Function Builder
=>se38 - ABAP Editor (to modify ABAP programs)
=>se39 - Split-Screen-Editor
=>se11 - ABAP Dictionary
=>se16 - Data Browser (Table contents display)
=>se41 - Menu Painter
=>se51 - Screen Painter
=>se71 - SAPScript Forms
=>se73 - SAPScript Font Maintenance
=>se75 - Graphic Objects and Graphic IDs Sapscript Settings
=>se78 - Administration of Form Graphics (Import Graphics into SAP System)
=>se80 - Object Navigator
=>se84 - ABAP Repository Information (search for SAP objects)
=>se91 - Message Maintenance
=>se93 - Maintain T codes
=>su01 - User Maintenance (Security)
=>su02 - Maintain Authorization Profiles
=>su03 - Maintain Authorizations
=>slg1 - Evaluate Application Log
=>sm12 - Lock Entries
=>sm21 - System Logs
=>sm36 - Background Job Scheduling
=>sm37 - Background Job Monitoring (display batch jobs)
=>sm31 - Table Maintenance
=>sm30 - Calling View Maintenance
=>sm35 - Batch Input Monitoring (Error Logs)
=>sm50 - Process Overview
=>sm58 - Transactional RFC Monitoring
=>sm59 - Maintain RFC Destinations (Define RFC Configuration)
=>snro - Number Range Objects (for IDOCs)
=>scc4 - Client Overview (Create, Quick Delete, Modify)
=>spro - Customizing, Execute Project
=>sp01 - Spool Administration
=>sq01 - Maintain SAP Queries
=>st02 - Buffer Analysis (Status Overview)
=>st03 - Workflow Analysis
=>st05 - Performance SQL trace (Tracking the Database calls from the System Transaction and Programs)
=>st22 - ABAP Dump Analysis, check logical runtime errors
=>/h - ABAP Debugger
=>we02 - Display IDOC
=>we05 - IDOC lists
=>we07 - IDOC statistics
=>we12 - Inbound processing of outbound file - convert outbound to inbound file
=>we14 - Process (dispatch) IDOCs through Port - RSEOUT00
=>we15 - Outbound IDOC from NAST - message control
=>we16 - Inbound File
=>we18 - Generate status file
=>we19 - Test tool
=>we20 - Add new Message Type to Partner Profile
=>we21 - Maintain Port Definition
=>we30 - IDOC Type development
=>we31 - IDOC Segment development
=>we41 - Process Code Outbound
=>we42 - Process Code Inbound
=>we46 - IDoc Administration
=>we47 - Status Code Maintenance
=>we57 - Assign function module to logical message and IDoc type
=>we63 - IDOC Type for Parser Output
=>we82 - Assign IDOC to Message Type
=>we60 - IDOC Documentation - IDOC Types
=>we61 - IDOC Documentation - IDOC Record Types
=>we81 - Create new IDOC Message Types
=>we82 - Assign IDOC to Message Type
=>pa20 - Display HR Master Data
=>pa30 - Maintain HR Master Data
=>bd59 - Create and assign Filter Object Type for Message Type
=>bd64 - Maintenance of ALE or any other Distribution Model
=>db02 - Storage Management and Database Performance
=>db14 - Database monitor
=>se18 - BADI definitions
=>se19 - BADI implementations
=>fd03 - Accounts Receivable Master Data (Display Customer in Accounting)
=>me22 - Change Purchase Order
=>me21 - Create Purchase Order
=>me51 - Create Purchase Requisition
Official source of SAP T Codes -Go to se11 or se16 and view table entries for
TSTC and TSTCT. This will give you the Transaction List.
Reward all helpfull answers
Regards
Pavan

HOW CAN I KNOW THE FUNCTION CODE OF CREATE NEW SESSION

HOW CAN I KNOW THE FUNCTION CODE OF CREATE NEW SESSION?
THANKS...

Hi
Please put a "/n" (to open a new session after killing the current session)
or "/o" (to open a new session without killing the current session)
or "/i" (to end the current session) before the below T Codes as per your requirement...
Try thistoo O0
demo-like programs
RSIMC000
RSIMC001
RSIMC002
RSIMC003
RSIMCTRX
RSIMCTST
Reward all helpfull answers
Regards
Pavan

Extracting the DDL(Code) of only stored procedures

DB Version:11g
I have a list of Stored procedures (about 250) whose code ie. CREATE OR REPLACE STORED PROCEDURE statements i want to extract to a file.
Is there an option in imp or impdp where i can extract only the code of these stored procedures?
Apart from imp/impdp , is there any other way to do this?

Is there an option in imp or impdp where i can extract only the code of these stored procedures?impdp, Yes. Write the contents to a file using, SQLFILE option.
DUMPFILE = exp.dmp
LOGFILE = exp.log
SCHEMAS=TEST
INCLUDE= PROCEDURE:"IN ('SP')"
SQLFILE=sp..sql
Or use dbms_metadata.get_ddl
set long 99999
set pagesize 0
SELECT DBMS_METADATA.GET_DDL(object_type, object_name, owner) FROM DBA_OBJECTS WHERE OBJECT_TYPE = 'PROCEDURE' and OWNER='OWNER';HTH
-Anantha

Using to pass the current user while creating a procedure

I have a .sql script that several people use to help set-up test beds but some users call the test procedures from a separate schema. The .sql creates a table (TABLE_A) and then a procedure that when run will create a trigger on a separate table (TABLE_B) that basically writes all info to TABLE_A. The problem is that if the .sql is run under schema SCOTT and then the procedure is run from schema JOE to create a trigger on JOE.TABLE_B, the trigger will try to write copy info to just TABLE_A instead of SCOTT.TABLE_A. My plan is to add a new input variable to the procedure for the schema where the procedure is located and set the default to the schema of the user running the .sql.
I can't seem to figure out how to call the current user and then pass it to a procedure as a DEFAULT input variable. Any help would be greatly appreciated.

OK, sadly, that did not work. What that provided to me was user that runs the procedure. If I run it as SCOTT it gives me SCOTT, but if I run as JOE, it gives me JOE.
I created an example of what I am trying to do (it is all run in a .sql file). Let me know if this is a bad example....
CREATE TABLE TABLE_A (
tranid VARCHAR2(20) Primary Key,
db_user varchar2(100) not null,
old_val varchar2(100) not null,
create or replace PROCEDURE TestBuild(OWN2 IN VARCHAR2, TNAME2 IN VARCHAR2, LOC2 IN VARCHAR2) IS
OWN VARCHAR2(30);
TNAME VARCHAR2(30);
FNAME VARCHAR2(62);
UNAME VARCHAR2(62);
COL VARCHAR2(30);
ST CHAR;
CONS VARCHAR2(30);
BEGIN
OWN := UPPER(OWN2);
TNAME := UPPER(TNAME2);
FNAME := OWN||'.'||TNAME;
UNAME := OWN||'_'||TNAME;
FILE := SYS.UTL_FILE.FOPEN(LOC2,'TEST_Trig_'||UNAME||'.sql','w');
SYS.UTL_FILE.PUT_LINE(FILE,'-- Test trigger start');
SYS.UTL_FILE.PUT_LINE(FILE,'-- generated '||SYSDATE);
SYS.UTL_FILE.NEW_LINE(FILE,1);
-- The following trigger fires for EVERY row of each statement for
-- the specified table.
SYS.UTL_FILE.PUT_LINE(FILE,'CREATE OR REPLACE TRIGGER Test_trig_'||UNAME||' AFTER INSERT OR UPDATE OR DELETE ON '||FNAME||' ');
SYS.UTL_FILE.PUT_LINE(FILE,' REFERENCING NEW as n OLD as o FOR EACH ROW');
SYS.UTL_FILE.PUT_LINE(FILE,' DECLARE');
SYS.UTL_FILE.PUT_LINE(FILE,' dmltype CHAR(1);');
SYS.UTL_FILE.PUT_LINE(FILE,' tpid VARCHAR2(30);');
SYS.UTL_FILE.PUT_LINE(FILE,' BEGIN');
SYS.UTL_FILE.PUT_LINE(FILE,' tpid := SYS.DBMS_TRANSACTION.LOCAL_TRANSACTION_ID();');
SYS.UTL_FILE.PUT_LINE(FILE,' IF INSERTING THEN dmltype := ''I'';');
SYS.UTL_FILE.PUT_LINE(FILE,' ELSIF UPDATING THEN dmltype := ''U'';');
SYS.UTL_FILE.PUT_LINE(FILE,' ELSIF DELETING THEN dmltype := ''D'';');
SYS.UTL_FILE.PUT_LINE(FILE,' END IF;');
SYS.UTL_FILE.PUT_LINE(FILE,' BEGIN');
SYS.UTL_FILE.PUT_LINE(FILE,' INSERT INTO TABLE_A VALUES (tpid,User,:o.col1);');
SYS.UTL_FILE.PUT_LINE(FILE,' END IF;');
SYS.UTL_FILE.PUT_LINE(FILE,' EXCEPTION WHEN already_there THEN NULL;');
SYS.UTL_FILE.PUT_LINE(FILE,' END;');
SYS.UTL_FILE.PUT_LINE(FILE,' END;');
SYS.UTL_FILE.PUT_LINE(FILE,'/');
SYS.UTL_FILE.PUT_LINE(FILE,'show errors');
SYS.UTL_FILE.NEW_LINE(FILE,1);
SYS.UTL_FILE.FCLOSE_ALL;
dbms_output.put_line('Script for table ['||FNAME||'] created. Now run it in sqlplus. ');
END;

Dunning procedure in configuration:Define Parametrize External Transactions

Hi There,
We can assign a Dunning Procedure in configuration at "Define and Parametrize External Transactions".
Path:
Financial Accounting->Contract Accounts Receivables and Payables->Basic Functions-> Posting and Documents->Document->Maintain Document Assignments-> Maintain Transactions for Non-Ind. Contract Accounts Receivables and Payables->Define and Parametrize External Transactions.
For every unique combination of Application Area, Company Code, Division, Main and Sub Transaction:
When you Add or Select an External Main and Sub transaction, on the Line Item Parameters you can add among other things - a Dunning Procedure and Dunning Lock reason. We cannot assign a Dunning Grouping here though.
I have been trying to figure out what the use is of assigning the Dunning procedure here.
1)In what business processes and when/where is this used? What circumstances is Dunning Procedure assigned at Transaction (Main and Sub) level?
2)Does this configuration insert the dunning procedure at the Item level? i.e all items created by this configuration (main and sub transaction) are configured with this Dunning Procedure or Dunning Lock Reason?
3)What advantages does it provide over assigning the dunning procedure to the Contract Account or Contract Object?
Thank you.

Hi,
1)In what business processes and when/where is this used? What circumstances is Dunning Procedure assigned at Transaction (Main and Sub) level?
Everytime a document item with this combintaion of transaction is created. It is a way to default some attributes when documents are posted. This dunning procedure has priority over the one filled in the contract account.
2)Does this configuration insert the dunning procedure at the Item level? i.e all items created by this configuration (main and sub transaction) are configured with this Dunning Procedure or Dunning Lock Reason?
Yes, this level has the highest priority (the specific level over the general level), and yes this configuration insert the dunning procedure at the item level
3)What advantages does it provide over assigning the dunning procedure to the Contract Account or Contract Object?
Well, it depends what do you want to get. Sometimes specific postings done in the contract account are required to be dunned using a different dunning procedure than the one filled in the contract account.The dunning procedure filled in the contract account is used by dafault to dunn all the contract account postings, but the postings with its own dunning procedure.

Dunning procedure in Vendor master

Why do we create Dunning procedure in Vendor master.. cud u pls advise..?
Txk
Umesh

3.3.3.4.1.2     Dunning Procedure
3.3.3.4.1.2.1     Defining Dunning Procedures
     Use
You enter the settings that control the dunning program by:
1.     Specifying the company codes to include in dunning.
2.     Setting up the dunning procedure you want to use (dunning interval, grace periods for the due date determination and number of dunning levels)
3.     Setting the dunning charges.
4.     Specifying the net payment due date at which a particular dunning level is reached.
5.     Specifying the dunning notice you want to send to your customers.
The following dunning procedures have been defined for dunning customers:
0001     Four-level dunning notice, every two weeks
Z030     Interest calculation after 30 days
The dunning procedure Z030 specifies that customers who do not pay within 30 days are automatically in arrears. The customers receive a dunning notice without interest amounts. From then on, interest is calculated for the open items using the interest calculation program (see also the section on the interest calculation program).
Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Dunning Procedure ® Define Dunning Procedures
2.     Choose New procedure.
3.     Make the following entries:
Field name     Entry
Dunn.Procedure     0001
Name     Four-level dunning notice, every two weeks
Dunning Interval in Days     014
No.of dunning levels     4
Total due items from dunning level
     3
Min.days in arrears (acct)
     6
Line item grace periods
     2
Public hol.cal.ID
     08
Interest indicator
     01
Standard transaction dunning     X
Ref.Dunning Procedure for Texts     0001
4.     Choose Dunning Levels.
5.     Maintain the following entries:
Field name     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Days in arrears     2     16     30     44
Calculate interest               X     X
Always dun                    X
Print all items               X     X
Payment deadline               10     7
6.     Choose Charges, enter currency EUR and make the following entries:
Field name     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Dunn.charge     5     5     10     10
7.     Choose Minimum Amounts, enter currency EUR and make the following entries:
Field name     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Minimum amount     1     2     5     10
Min.amt for interest     1     5     10     10
8.     Choose Dunning Texts, enter company code BP01 and choose account type customer. Make the following entries:
Field     Dunning level 1     Dunning level 2     Dunning level 3     Dunning level 4
Form     Z_F150_DUNN_01     Z_F150_DUNN_01     Z_F150_DUNN_02     Z_F150_DUNN_02
9.     Choose Save.
10.     Choose Back and maintain the next dunning procedure.
11.     Choose New procedure.
12.     Make the following entries:
Field name     Entry
Dunn.Procedure     Z030
Name     Interest Calculation after 30 days
Dunning Interval in Days     014
No.of dunning levels     2
Public hol.cal.ID
     08
Interest indicator
     01
Standard transaction dunning     X
Ref.Dunning Procedure for Texts     Z030
13.     Choose Dunning Levels.
14.      Maintain the following entries:
Field name     Dunning level 1     Dunning level 2
Days in arrears          14
Calculate interest     X     X
Print all items     X     X
Payment deadline     7
15.      Choose Dunning Texts, enter company code BP01 and choose account type customer.
16.      Make the following entries:
Field name     Dunning level 1     Dunning level 2
Form     Z_F150_DUNN_04     Z_F150_DUNN_04
17.      Choose Save.
3.3.3.4.1.2.2     Defining Dunning Procedures
     Use
In this activity you enter the settings that control the dunning program.
     Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Dunning Procedure ® Define Dunning Procedures
2.     Choose the menu Environment ® Company Code Data and make the following entries:
Company Code     Dunning by Area     Separate Dunn. Notice     Ref. Comp. Code      Sort. Variant Acct     Sort. Variant Items     Dunn. Comp. code
BP01               BP01     K1     P1     BP01
3.3.3.4.1.2.3     Defining Interest Rates
     Use
In the dunning program, an interest rate of 7.68% has been defined for interest indicator 01 and the currency EUR. This interest rate is the same as the rate set for the interest calculation program and is calculated from the discount rate (2.68%) and a surcharge of 5%.
     Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Dunning Procedure ® Define Interest Rates
2.     Make the following entries:
Interest Indicator     Currency     Valid from     Debit Interest     Credit Interest
01          01.01.1991     7.680     7.680
01     PHP     01.01.1991     7.680     7.680
3.3.3.4.2     Printout
3.3.3.4.2.1     Defining Sender Details for Dunning Forms
     Use
In this activity, you define which standard texts are used for the header, the footer, and the sender address in the letter window for each company code.
     Procedure
1.     Access the activity using one of the following navigation option:
Transaction code     SPRO
IMG menu     Financial Accounting (NEW) ® Accounts Receivable/
Accounts Payable ® Business Transactions ® Dunning ® Printout ® Define Sender Details for Dunning Forms
2.     Make the following entries:
Dunning Area     Text ID     Header Text     Footer Text     Signature Text     Sender
     ADRS     ADRS_HEADER     ADRS_FOOTER     ADRS_SIGNATURE     ADRS_SENDER
3.3.3.4.2.2     Allowing Dunning with SAP script Forms
     Use
You have the possibility to use either SAP script forms or Smart Forms in the dunning procedure. In this transaction you have to specify which forms are used for dunning in this system.
This table is cross-client. Any changes you make in this table will take effect in all clients of your system.
     Prerequisites
You have processed the previous mentioned steps.
     Procedure
1.     Access the activity using one of the following navigation options:
Transaction code     BF31
IMG menu     Financial Accounting (NEW)  Financial Accounting Global Settings (New)  Tools  Customer Enhancements  Business Transaction Events  Settings  P/S Function Modules  u2026 of an SAP appl.
2.     On the Change View Publish & Subscribe BTE: SAP Enhancement: Overview screen, check - and if necessary change - the following entries:
Field name     Description     User action and values     Notes
Event     Event (Business Transaction Event)     00001720     this entry already exists
Country     Ctr (Country ISO Code)     Blank
Appl.     Appl. (Application Indicator for BTE)     FI-FI
Funct     Function Module     FI_PRINT_DUNNING_NOTICE     this function module needs to be entered if SAPSCRIPT forms should be used
3.     Choose Save.
If you want to use Smart Forms then you have to enter for above mentioned event 00001720 function module FI_PRINT_DUNNING_NOTICE_SMARTF. Please be aware that in installation guide and configuration guide the set up for customizing is only made for dunning with SAP script forms and not for dunning with Smart Forms.

Dunning Procedure not creatd

Hi Fi Experts
While creating a dunning procedure, after giving all the details in the very first screen, then when i am clicking on the dunning texts n giving the New co. cd its not allowing me to save giving a error tht (This syntax cannot be used for an object name)**
rgds
Raj

Hi
For creating Dunning Procedure
select new procedure button.
Give dunning procedure , give Name , give dunning intervals in days , no. of dunning levels ,
line item grace periods , interest indicator.
select standard transaction dunning check box.
Give Ref. Dunning Procedure for texts (same dunning procedure).
and save it. now you will get a message. ignore and enter.
select dunning text button , give company code , select customer radio button and enter.
select new company code button and give company code and enter.
Here you select seperate notice per dunning level check box.
Dont select dunning by dunning area and save it.
definitely this will work out.
Regards
Venkat

The tax code entered is not defined in the company code country.

Dear sap guru's
I am facing a problem while doing invoice or while cancelling the invoice or even during Subsequent Credit/Debit
Tax code V0 in procedure is invalid
   Message no. FF704
Diagnosis
   The tax code entered is not defined in the company code country.
System Response
Procedure
   Check and, if necessary, correct the entry.
Procedure for System Administration
   If it is not an input error, check and possibly change the system
   settings.
   To do this, choose Maintain entries (F5).
   1. Check whether the required tax procedure has been allocated to the
       company code country. The Procedure field is on the detailed screen.
   2. If you need a new tax code, you can create one yourself.
For this i have checked the assignment of company code and tax code V0 in Tcode (OBCL)
In FTXP the tax code is created in country IN, for the same tax procedure and the tax is a input tax.
please suggest what could be the exact problem
Regards
Sujit

Hi Sujit,
1.Go to FTXP and create tax code V0 for country IN and procedure ZAXINN.
2.In Txn: FV11, For the condition type- XXXX (You will get this in Txn: FTXP, against the tax type, you get the condition type OR in the PO-Item details- Invoice tab, next to field: Tax code, see the Tab-Taxes, click on it and will get the condition type) , maintain the country-IN, Tax code-V0 and the rate.
3.Also things to be checked
1> assign country to company code
2> assign company code to tax code
3> create tax code for country IN
4.Under the following menu path, pls check if you have assigned your tax code to Company Code
IMG>Logistics (General)>Tax on Goods Movement>India>Basic Settings>Determination of Excise Duty>Condition Based Excise Determination>Assign Tax Codes to Company Code
Hope it clears,
Rahul.

Deleting Dunning Procedure Data Off Customer Master

Hi
I am using transaction FD02 for a customer which has had dunning run against it in the past. I want to change the Dunning Area and Dunning Procedure for this customer.
I go to the Correspondence tab and change the Dunn. Procedure. I then click on Dunning Areas and see two entries - one has a Dunning Procedure and no Dunning Area and the other has both a Dunning Procedure and a Dunning Area. I want to delete the entry without the Dunning Area as I need the Dunning Area later for reading a custom table.
When I try to delete the entry with the Dunning Procedure but no Dunning Area I get the error message: F2117 Delete all dunning area data first
What should I do?
Thank you
Gill

Hi
Thank you for the response however I have 2 problems with this program:
1) It requires a code change to had code the user name of the person who is allowed to run it in update mode. I would have problems getting this though our change control process
2) As far as I can tell its purpose is to delete past dunning information. I would like to retain the historical information about dunning for each customer
Is there anything else I can do?
Thank you
Gill

HOW TO CREATE STORED PROCEDURE IN DATA INTEGRATOR

Hi to every one,
Can any one help in giving me a solution for creating stored procedure in Data Integrator.
I m new to this field

Hi nath,
Firstly are you using MYSQL or Oracle as the database,if its oracle database then follow this
http://obiee101.blogspot.com/2008/01/obiee-using-oracle-stored-procedure-to.html
http://oraclebizint.wordpress.com/2008/02/20/oracle-bi-ee-101332-executing-stored-proceduresfunctions-before-reports-before-report-triggers-and-global-temporary-tables/
EXEC [DATABASE_NAME].[SCHEMA_NAME].[PROCEDURE_NAME][DATABASE_NAME] --> is the database name your creating your procedure
[SCHEMA_NAME]-->is the user with which your creating
[PROCEDURE_NAME] --> the name given to procedure
You dont know how to get those run this SQL in TOAD and see select sys_context('userenv','db_name'), sys_context('userenv','session_user') from dual
(OR) open you connection pool properties window in RPD,you will get the DB name and the user name as the schema name
hope answered your question.
CHeers,
KK

Transaction code to create virtual interface.

I want to create a web service from a RFC. For that first, virtual interface needs to be created which will be linked to the RFC. Can u please tell me what is the transaction code to create a virtual interface.

Thankx for ur reply.
Now I have created the Web service. To do this I have done the followings-
1. created one RFC enabled Function Module.
2. Created one virtual interface
3. Created Web service defination.
4. Released Web service from the wsconfig transaction.
Then from The transaction wsadmin I have opened the browser by clicking Web Service > Web Service Homepage (from menu)
After logging in it , shows the web service and RFC with in it. Now after clicking the Test link from the browser it asks for the parameter of the RFC. But After populating the parameters and clicking send button. it gives NullpointerException.
exact err message is --
An error has occurred. Maybe the request is not accepted by the server:
java.lang.NullPointerException

T-code for creating new payment term

Dear All,
What is the T-code for creating new payment term in PO.
Pleaze reply it soon.
Thanks
Prasant Sekhar

use /NOME2.here u can create or copy as u wish.
regards,
indranil

How the Queue will be created to process the Multiple IDOC's into 1 Queue

Hi Sap All.
when i went into the Transaction code we14 and when the press F4 for search help in the field Queue Name it displays me the several queues with the Port referring to B0018(refers to PI Box) ,which means that the IDOC's will be sending to PI.
here my Question is how the Queues get created ,what is the Transaction code for creating the Queues in SAP-R/3 and how we we setup the SAP-R/3 Box in order to send multiple IDOC's into one queue.overall my question is how we wrok on Queues ?
could any body help me in driving me to the best way.
regards.
Seetharam.

If you have the drivers CD or the LV 6 installation CD, then you could try installing just the traditional DAQ drivers. I will do a search if I can find them...Good news, I found the drivers that you may need. Here is the link to download.
After you install it, look in the vi.lib folder for the DAQ folder and see if you have a dozen
.llb files. That is where you will find your missing vi's. You may also check into the LV2009 folder to check to
see if the driver got installed there. I think the driver only gets
installed for a single version and it might default to the latest at that time (I did not check which one it was).
In any case, look for the missing VIs in the \National Instruments\LabVIEW 2009\vi.lib\Daq\ folder. The VIs are contained in the .llb files so you
can't just search for them through Windows. Look in the AI.llb file using LabVIEW.
Here are issues that you may encounter. The link is to the DAQmx driver (I thought it was for traditional DAQ )
http://forums.ni.com/t5/LabVIEW/Error-10461-10008-DIO-Port-Config-Legacy-lvdaq-dll/m-p/947104
Someone with a similar problem. It won't help you, but kinda explains what you are going through..
http://forums.ni.com/t5/LabVIEW/Since-upgrading-labview-many-sub-vi-s-such-as-DIO-Port-Config-vi/m-p...
Although the recommendation in this thread is to use the same LV version and driver as the previous machine, we know it is not your case. Newer LV version... and maybe the latest Traditional DAQ drivers... May be worth reading:
http://forums.ni.com/t5/LabVIEW/An-error-occurred-loading-VI-AI-Group-Config-vi/m-p/734547
Traditional DAQ 7.4.4
http://digital.ni.com/softlib.nsf/websearch/E42B7A3564AB2F1A862572A7006D1564?OpenDocument

The T-code of creating dunning procedure

Similar Messages

Maybe you are looking for