What are the mandatory fields needed to setup/register the SIP phone manually in CUCM

What are the mandatory fields needed to setup/register the SIP phone manually.Also, if someone can let me know the mandatory fields for Cisco based SIP phone and also the third party SIP hard phones like Avaya or any other Third party SIP phones both Soft phone and physical phone requirements...in CUCM
Please suggest...I need to know if MAC address is mandatory for all Cisco SIP phone to setup

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-cm/b09sip3p.html
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-70/112110-phone-add-00.html

Similar Messages

What are the Mandatory Fields in Transaction ME51

Hello Seniors,
I have a requirement about purchase order creation. In this process, I am using the BAPI named " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2" and I see an error which reads "" All mandatory fields are missing"". I have even created a PO in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
Your reply is most awaited and rewarded.
Thanks and Regards,
MARKIV

hi ,
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
regards
reena

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

What and Which are the Mandatory fields in a Purchase Order?

Please advise how I can check what the Mandatory fields are in a purchase order and which fields are not Mandatory ?
Also, Please advise where this information can be found in the manual?
Thanks in advance.
Edited by: Darpal Thiarha on Feb 26, 2008 3:49 PM

Hi,
mandatory fields are:
vendor
docdate
delivery date
and other fields you may test in sbo_transactionnotification procedure.
I don`t think that this is written in manual, you have to test to add the document with few fields filled and check it.
Petr

What are the mandatory fields in DTW for opening balances imports?

Hi All,
As the title mentions could you please help by listing all the mandatory fields in DTW for importing opening balances ?
Thank you for your help,
MB

Hi Gordon and all,
I have a look at the SDk help files and almost cried but am i right in thinking it is Account Code, Debit and Credit fields that are the mandatory fields for opening balances?
These sdk help files are awful by the way...really awful.
MB

What are all the mandatory fields of the BAPI_PO_GETDETAIL?

Hi friends,
I am new to XI. I am using the "BAPI_PO_GETDETAIL1" in my scenario to get details of a particular Purchase Order. Can you tell me the mandatory fields of this BAPI?
Where should i look to identify the mandatory fields of a BAPI?
Thanks.
Senthil Nathan.

Hi you can see this in SE37 under the Import Tab. Here you see that the only mandatory input field is PURCHASEORDER. So if you provide the purchaseorder number you get alle the details for that.
Kind regards
Mikkel

I need to setup 7800 Series IP Phones in the CUCM 8.6.2 which by default are not support but will work after install the software. Anyone have document from Cisco as I remember I seen once before.

I need to setup 7800 Series IP Phones in the CUCM 8.6.2 which by default are not support but will work after install the software. Anyone have document from Cisco as I remember I seen once before.

Hi Ali,
I'll just add this reference to the good tips from my friend Manish (+5)
Support for the 7800 series in CUCM 8.6.2 was first added with this
Device Pack;
Cisco Unified Communications Manager
Device Package 8.6(2)(24104-1)Release Notes
Cisco Unified Communications Manager Device Package Release 8.6(2)
adds support for the Cisco IP Phones
7821, 7841, and 7861 running SIP firmware release 10.1(1).
The steps are in this doc
http://www.cisco.com/web/software/282074299/107528/cmterm-devicepack-8.6.2.24104-1_Readme.pdf
You might as well install the latest 8.6.2 Device pack
cmterm-devicepack8.6.2.24112-1.cop.sgn
Cheers!
Rob
"Seek it out and ye shall find "
- OneRepublic

Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST

hi all ,
Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST
what all data i need to give to post a document.
Thanks and Regards
JK

Hi...
part of my source code:
** Header Data " Sending comp code
wa_documentheader-comp_code = 'XXXXX'.
wa_documentheader-doc_date = '20060620'.
wa_documentheader-pstng_date = '20060620'.
wa_documentheader-doc_type = 'XX'.
wa_documentheader-username = sy-uname.
wa_documentheader-ref_doc_no = 'XXxxxxxx'.
wa_documentheader-header_txt = 'Text Header.
wa_documentheader-bus_act = 'XXXX'.
*it_currencyamount
wa_currencyamount-itemno_acc = '1'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = 1943.
APPEND wa_currencyamount TO it_currencyamount.
*it_accountpayable
wa_accountpayable-itemno_acc = '1'.
wa_accountpayable-gl_account = '1234567890'.
wa_accountpayable-bus_area = 'DIV'.
wa_accountpayable-item_text = 'Text 1 XXxxxxx '.
wa_accountpayable-pmnt_block = ''.
APPEND wa_accountpayable TO it_accountpayable.
*it_accountgl
wa_accountgl-itemno_acc = '2'.
wa_accountgl-gl_account = '1234567890'.
wa_accountgl-item_text = 'Text 2 XXxxxxx'.
wa_accountgl-bus_area = 'DIV'.
APPEND wa_accountgl TO it_accountgl.
wa_currencyamount-itemno_acc = '2'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = ( 1943 ) * -1.
APPEND wa_currencyamount TO it_currencyamount.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
EXPORTING
    documentheader = wa_documentheader
TABLES
    accountgl      = it_accountgl
    accountpayable = it_accountpayable
    currencyamount = it_currencyamount
    return         = it_return.
clear it_return.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
      EXPORTING
        documentheader = wa_documentheader
      TABLES
        return         = it_return
        currencyamount = it_currencyamount "currencyamount
        accountpayable = it_accountpayable "accountpayable
        accountgl      = it_accountgl "accountgl
      EXCEPTIONS
        OTHERS         = 01.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Mandatory fields & JHS different behavior for the very same situation

Hi,
There is an issue regarding mandatory fields in a form. Let me put it in this way:
Using this framework, obviously there are two ways for declaring a field as a mandatory one.
Firstly, at model level; checking the mandatory check box in the entity itself and secondly; at view level; one can set the required field in application definition.
The problem is; leaving a mandatory field empty; the user faces two different alert messages_.
Best Regards,
Yasaman Parandian
Edited by: Parandian on Oct 7, 2009 5:02 AM

Steven,
I can see a little bit of misunderstanding here; the point is that the javascript alert message is
the preferable behavior……And the question is if there is any way that I can change the JHS-level mandatory fields to pop up a javascript error message when left empty.
Thank you so much in advance,
Best Rgrds
Yasaman Parandian

IW31 how to set functional area as mandatory field?

Hi,
Can anyone guide me, is any way to set "functional area" as mandatory field (t-code iw31 Additional Data -> Functional area)? Thanks in advance.

go to the config:
SPRO: PM & CS -> Maint. & Serv. Processing -> Maint. and Service Orders -> Define Field Selection for Order Header Data (PM)
...Choose "Field Selection for order header data"
...toggle to change mode (use menu "field selection at the top left". Then find your field (functional area CAUFVD-FUNC_AREA) and put the radio button to "required"
This will make it mandatory for all order types. If you want only specific order types, use the influencing fields to pick only certain order types.

How to remove the mandatory field setting in output control

Hi everybody,
While printing a Payment Voucher through F-58 and FBZ5(reprint), there are two output devices, the first one is - printer for forms and second is - payment advice printer.
In our case we have configured the cheque printing and payment voucher printing seperately. The cheque goes to first printer(kept mandatory field) and the payment voucher goes to second printer. One of our plant does not print the cheque from SAP, they only print the payment voucher because the cheque is manually prepared. How do I avoid the cheque printing. Is there any way out to print only the payment voucher through F-58 and FBZ5
Please guide me how to tackle it or how to remove the mandatory field setting in the output control screen?
Regards
Paul

Hi
As of my understanding, there is no relation ship between the Sales Organization and this mandatory partner function.
Here are few suggestions.
1. Since Partner functions are defualted and made mandatory in the Partner Determination Procedure so you have to remove this Mandatory option for PE from the Partner Determination Procedure that is AG if using standard one.
2. If you are using a single partner function than , Copy and create a New partner procedure and a new account group . Where in one you can default PE as mandatory and in another one you make a optional where it can be choosen manually while creating the customer.
Follow the path to check for entries :
SPRO > sales & distribution > Basic Function > Partner Determination > set up partner determination > select for customer master > select the partner procedure you are using AG as standard > then partner function in procedure > here maintian the check as required like, Mandatory or No check for Non Mandatory .
Thanks
RB

Hide the error msg for the mandatory fields

hi
how can i hide the error msg for the mandatory fields when they are not entered?? when i don't put a value in a mandatory field and commit the form, an error msg occurs teelling to enter the value for that mandatory field, but the error msg is not friendly at all and i want to hide it.
thnaks

User,
I'll assume you are talking about ADF Faces + ADF Business Components application, since you don't mention it.
If you are talking about the pop-up Javascript dialog box that pops up, you can do the following:
1). Set required=false on those fields in your JSP.
2). Set showrequired=true on those same fields so that there is a visual indication that the fields are required
3). Ensure the attribute to which the fields are bound have "mandatory" set to true in the BC's
Now, when you commit the form, you will not see the Javascript pop-up, but you will see a message in the af:messages component.
Best,
john

I would make the signature field read only until something is entered in the mandatory fields.

I would make the signature field read only until something is entered in the mandatory fields.

Mina,
You can use LiveCycle Designer's Action Builder to easily achieve this.
Please go through online documentation for the specific version of LiveCycle Designer that you are using.
It is intuitive and very easy to use Action Builder (You will find this option under Tools Menu item of Designer).
--Santosh

I copied message to SMS field and sent. After that the message still exist all the time in the SMS field. When I open the application I must always first delete the "saved" ones before I write the new one. What to do to finally/definitely delete the save

I copied message to SMS field and sent. After that the message still exist all the time in the SMS field. When I open the application I must always first delete the “saved” ones before I write the new one. What to do to finally/definitely delete the save message?

sorry it's ios6

Any way to validate the Mandatory field in the XML file

Hi,
Is there any way to validate the Mandatory field in the XML file. I created an xml type table xml_validate based on the schema and insert the XML files with statement.
INSERT INTO xml_validate(warehouse_id,xml_file_name,warehouse_spec)
Values (agreementid,p_filename,XMLTYPE.createXML(l_clob));
It is validating the data types, extra tags etc but not validating the missing of the manadatory tag/value.
Thanks in advance
Rizly

Hi Ants,
Yes, I was not doing the strict validation, after searching the forum i understood that was the reason. So i did this way,
begin
for x in (select myColumn from myTable where WAREHOUSE_ID=41) loop
x.myColumn .schemaValidate();
end loop;
end;
The out put is:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00011: internal error: LsxvPushCandidate array overflow
ORA-06512: at "SYS.XMLTYPE", line 345
ORA-06512: at line 3
My i know more information about this error, especially
LSX-00011: internal error: LsxvPushCandidate array overflow
Thanks in advance
Rizly

What are the mandatory fields needed to setup/register the SIP phone manually in CUCM

Similar Messages

Maybe you are looking for