Academic Title

Hallo
I am trying to collect the Academic Title of the contact person in Transection VA22 (Quotation). I have tables TSAD2 and knvk . How can I collect the title from these
two tables or is there any ??
regards
rana

Hi Anne,
do you have created an attribute context for mail forms?
if not, you can find it here:
SPRO-CRM-Marketing-Marketing Plannig and Campaign Management-Personalized Mail-Maintain Attribute Context for Mail Forms.
There you can create your own stuctures for your mail forms.
If I remind right, you can choose these attributes as "additional attributes" while creating a mail form.
Regards,
Dennis

Similar Messages

Error in Mail Form: Academic titles

Hi All,
I have included the fields
1. Title_Key and
2. Title_Aca1 from the BP_Structures in my mail form.
My mail form is in a different language. Thus, the requirement is to have the Title and Academic Title in the other language.
I have maintained the entries in the other language too.
Even if i log in in another language, the Title is taken as (Mr.) or (Ms.)instead of (Herr) or (Frau)
Thus, i want to know, why this is happening and how can i solve this issue. Am i missing something in customization or in maintaining any flag for the language etc.
Thanks,
Kedar
Edited by: Kedar Toraskar on May 30, 2008 11:35 AM
Edited by: Kedar Toraskar on May 30, 2008 11:35 AM

Hi Kedar,
The language priority in the mail form, during the campaign execution are as given below:
- For Person (B2C Scenario)
Prio 1. the field 'Correspondence lang.' in business partner 'Address' field group 'Detail information'
Prio 2. The field 'Language' in the business partner 'Address' data, field group 'Name'.
Prio 3.Log-on language.
- For Organization (B2B Scenario)
Prio 1. The field 'Language' in the business partner 'Address' data, field group 'Communication'.
Prio 2.Log-on language
- For Contact person for organization (B2B)
Prio 1. The field 'Correspondence lang.' in business partner (contact person) 'Central data' -> 'Detail information'. Same language are displayed on the 'Relationship' screen, field 'Language' on the 'Details' data to the relationship, field group 'Communication'.
Prio 2. The 'Relationship' data for business partners, field 'Language' on the 'Detail' data to the relationship , field group 'Company'. (= communication language of organization)
Prio 3. The field 'Language' in the business partner (contact person) 'Address' data, field group 'Name'.
Prio 4.Log-on language.
Please check whether you have maintained languages correspondingly
For more information on this, refer to SAP Notes 708355.
regards
Srikantan

Academic Title in Mail Forms

Hi all,
just a short question about mail forms.
We use the mail form for file export, there in the standard attributes you can choose the academic titlle. When you start the campaign with that mail form the system will give you the description of the academic title (Data element AD_TITLE1D) and not the academic title (Data element: AD_TITLE1T) itself. So for example you have Professor instead of Prof. But nobody wants to be addressed as Professor Doctor Maier on a letter but as Prof. Dr. Maier.
Has anyone of you an idea how we can get the short version of the academic title (AD_TITLE1T) in our mail form?
Thanks in advance!
Regards Anne

Hi Anne,
do you have created an attribute context for mail forms?
if not, you can find it here:
SPRO-CRM-Marketing-Marketing Plannig and Campaign Management-Personalized Mail-Maintain Attribute Context for Mail Forms.
There you can create your own stuctures for your mail forms.
If I remind right, you can choose these attributes as "additional attributes" while creating a mail form.
Regards,
Dennis

Dropdown for Title key and academic title

Hi Experts,
How to provide a Dropdown for Title and Academic Title fields in the component ICCMP_BP_DETAIL, View: BupaDetailB2B, Contextnode: Customer, Attribute:Struct.Title_Key. The field is of type input field but, i want to make it as picklist.Please suggest some Inputs.I am functional guy, so please try to give detailed solution.Thanks in advance.
Regards
Krish

Hi Krishna,
As far as I can see this note provides the TITLE_KEY dropdrown list... that's cool.
Then what is exactly that you don't understand ? After applying the note you just need to add the TITLE_KEY field to your configuration to make it appear on the screen... (and SAP suggests to use object subtypes in your configuration criterias to make this field appear under certain circumstances only -- but it is not mandatory).
Nicolas.

Title in CMR

Hi Friends,
In CMR, general data, title field has the selection options like company, Mrs. etc........If we want to creat our own text, where do we do it. are there any configuration steps?
Thanx and Regards
Samatha

hi,
pl check these transactions :
Systems Transactions
SA01 Number range maintenance: ADRNR
SA02 Academic title (cent. addr. admin.)
SA03 Title (central address admin.) - to meet your req
SA04 Name prefixes (centr. addr. admin.)
SA05 Name suffix (centr. addr. admin.)
SA06 Address or personal data source
SA07 Address groups (centr. addr. admin.)
SA08 Person groups (centr. addr. admin.)
SA09 Internat. versions address admin.
SA10 Address admin. communication type
regards
sadhu kishore

Syntax error in Transformation routine

Hi Folks,
We are In SP 17.
I have migrated standard 0bpartner_attr transfer rules to a transformation with syntax errors.
I have a routine for a gender, Valid From and Valid To its giving the following erorr.
E:Field "TRAN_STRUCTURE-VALID_FROM" is unknown. It is neither in one of
the specified tables nor defined by a "DATA" statement. "DATA"
statement.
the following is the routine code for Gender.
PROGRAM trans_routine.
 CLASS routine DEFINITION
CLASS lcl_transform DEFINITION.
PUBLIC SECTION.
Attributs
 DATA:
 p_check_master_data_exist
 TYPE RSODSOCHECKONLY READ-ONLY,
*- Instance for getting request runtime attributs;
 Available information: Refer to methods of
 interface 'if_rsbk_request_admintab_view'
 p_r_request
 TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
PRIVATE SECTION.
 TYPE-POOLS: rsd, rstr.
Rule specific types
 TYPES:
 BEGIN OF tys_SC_1,
 Field: XSEXM Male.
 XSEXM TYPE C LENGTH 1,
 Field: XSEXF Female.
 XSEXF TYPE C LENGTH 1,
 Field: XSEXU Unknown.
 XSEXU TYPE C LENGTH 1,
 Field: RECORD.
 RECORD TYPE RSARECORD,
 END OF tys_SC_1.
 TYPES:
 BEGIN OF tys_TG_1,
 InfoObject: 0GENDER Gender.
 GENDER TYPE /BI0/OIGENDER,
 END OF tys_TG_1.
$$ begin of global - insert your declaration only below this line -
... "insert your code here
$$ end of global - insert your declaration only before this line -
 METHODS
 compute_0GENDER
 IMPORTING
 request type rsrequest
 datapackid type rsdatapid
 SOURCE_FIELDS type tys_SC_1
 EXPORTING
 RESULT type tys_TG_1-GENDER
 monitor type rstr_ty_t_monitor
 RAISING
 cx_rsrout_abort
 cx_rsrout_skip_record
 cx_rsrout_skip_val.
 METHODS
 invert_0GENDER
 IMPORTING
 i_th_fields_outbound TYPE rstran_t_field_inv
 i_r_selset_outbound TYPE REF TO cl_rsmds_set
 i_is_main_selection TYPE rs_bool
 i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
 i_r_universe_inbound TYPE REF TO cl_rsmds_universe
 CHANGING
 c_th_fields_inbound TYPE rstran_t_field_inv
 c_r_selset_inbound TYPE REF TO cl_rsmds_set
 c_exact TYPE rs_bool.
ENDCLASS. "routine DEFINITION
$$ begin of 2nd part global - insert your code only below this line *
$$ end of rule type
 TYPES:
 BEGIN OF tys_TG_1_full,
 InfoObject: 0BPARTNER Business Partner.
 BPARTNER TYPE /BI0/OIBPARTNER,
 InfoObject: 0BP_ACTITL1 First Academic Title.
 BP_ACTITL1 TYPE /BI0/OIBP_ACTITL1,
 InfoObject: 0BP_ACTITL2 Second Academic Title.
 BP_ACTITL2 TYPE /BI0/OIBP_ACTITL2,
 InfoObject: 0BP_BTHNAME BP: Person's Name at Birth.
 BP_BTHNAME TYPE /BI0/OIBP_BTHNAME,
 InfoObject: 0BP_CAT Business Partner Category.
 BP_CAT TYPE /BI0/OIBP_CAT,
 InfoObject: 0BP_CONS Business Partner (Consolidated/Cleansing).
 BP_CONS TYPE /BI0/OIBP_CONS,
 InfoObject: 0BP_CONTACT BP: Contact Permission.
 BP_CONTACT TYPE /BI0/OIBP_CONTACT,
 InfoObject: 0BP_EXTERN BP Number in External System.
 BP_EXTERN TYPE /BI0/OIBP_EXTERN,
 InfoObject: 0BP_FSTNAME BP: Person's First Name.
 BP_FSTNAME TYPE /BI0/OIBP_FSTNAME,
 InfoObject: 0BP_GROUP Business Partner Grouping.
 BP_GROUP TYPE /BI0/OIBP_GROUP,
 InfoObject: 0BP_GRPNAM1 BP: Name 1 (Group).
 BP_GRPNAM1 TYPE /BI0/OIBP_GRPNAM1,
 InfoObject: 0BP_GRPNAM2 BP: Name 2 (Group).
 BP_GRPNAM2 TYPE /BI0/OIBP_GRPNAM2,
 InfoObject: 0BP_GRPTYPE BP: Group Type.
 BP_GRPTYPE TYPE /BI0/OIBP_GRPTYPE,
 InfoObject: 0BP_LSTNAME BP: Person's Surname.
 BP_LSTNAME TYPE /BI0/OIBP_LSTNAME,
 InfoObject: 0BP_MAR_STA BP: Marital Status.
 BP_MAR_STA TYPE /BI0/OIBP_MAR_STA,
 InfoObject: 0BP_MDLNAME BP: Person's Middle Name or Second First
*Name.
 BP_MDLNAME TYPE /BI0/OIBP_MDLNAME,
 InfoObject: 0BP_SECNAME BP: Person's Second Surname.
 BP_SECNAME TYPE /BI0/OIBP_SECNAME,
 InfoObject: 0CHANGEDBY Changed by.
 CHANGEDBY TYPE /BI0/OICHANGEDBY,
 InfoObject: 0CH_AT Time of Last Change.
 CH_AT TYPE /BI0/OICH_AT,
 InfoObject: 0CH_ON Last changed on.
 CH_ON TYPE /BI0/OICH_ON,
 InfoObject: 0CREATEDBY Name of person who created the object.
 CREATEDBY TYPE /BI0/OICREATEDBY,
 InfoObject: 0CREATEDON Date on which the record was created.
 CREATEDON TYPE /BI0/OICREATEDON,
 InfoObject: 0CREA_TIME Time Created.
 CREA_TIME TYPE /BI0/OICREA_TIME,
 InfoObject: 0GENDER Gender.
 GENDER TYPE /BI0/OIGENDER,
 InfoObject: 0LEGALFORM Legal Status of Organization.
 LEGALFORM TYPE /BI0/OILEGALFORM,
 InfoObject: 0NAME_ORG1 BP: Organization Name 1.
 NAME_ORG1 TYPE /BI0/OINAME_ORG1,
 InfoObject: 0NAME_ORG2 BP: Organization Name 2.
 NAME_ORG2 TYPE /BI0/OINAME_ORG2,
 InfoObject: 0NAME_ORG3 BP: Organization Name 3.
 NAME_ORG3 TYPE /BI0/OINAME_ORG3,
 InfoObject: 0NAME_ORG4 BP: Organization Name 4.
 NAME_ORG4 TYPE /BI0/OINAME_ORG4,
 InfoObject: 0NATION Nationality.
 NATION TYPE /BI0/OINATION,
 InfoObject: 0TITLE_SPPL Name Supplement, for example, Noble Title
 TITLE_SPPL TYPE /BI0/OITITLE_SPPL,
 InfoObject: 0BP_TYPE Partner:Partner Type.
 BP_TYPE TYPE /BI0/OIBP_TYPE,
 InfoObject: 0GN_PAR_SSY Source System of a Partner.
 GN_PAR_SSY TYPE /BI0/OIGN_PAR_SSY,
 InfoObject: 0LOGSYS Source System.
 LOGSYS TYPE RSDLOGSYS,
 InfoObject: 0RECORDMODE BW Delta Process: Record Mode.
 RECORDMODE TYPE RODMUPDMOD,
 InfoObject: 0BP_GUID GUID of Business Partner.
 BP_GUID TYPE /BI0/OIBP_GUID,
 InfoObject: 0BPDATEFROM GP Attributes Valid from.
 BPDATEFROM TYPE /BI0/OIBPDATEFROM,
 InfoObject: 0BPDATETO GP Attributes Valid to.
 BPDATETO TYPE /BI0/OIBPDATETO,
 Field: RECORD Data record number.
 RECORD TYPE RSARECORD,
 END OF tys_TG_1_full.
Additional declaration for transfer rule interface
DATA:
 g_t_errorlog TYPE rssm_t_errorlog_int,
 RECORD_ALL LIKE SY-TABIX.
global definitions from transfer rules
DATA: gs_cob_pro TYPE rsd_s_cob_pro,
 gt_viobj TYPE rsd_t_viobj,
 gs_viobj TYPE rsd_s_viobj.
DATA: l_s_errorlog TYPE rssm_s_errorlog_int,
 l_text TYPE string.
FORM compute_BPDATEFROM
 CHANGING
 RESULT TYPE tys_TG_1_full-BPDATEFROM
 RETURNCODE LIKE sy-subrc
 ABORT LIKE sy-subrc
RAISING
 cx_sy_arithmetic_error
 cx_sy_conversion_error.
INCLUDE rs_bct_bupa_form_valid_from.
ENDFORM. "BPDATEFROM
FORM compute_BPDATETO
 CHANGING
 RESULT TYPE tys_TG_1_full-BPDATETO
 RETURNCODE LIKE sy-subrc
 ABORT LIKE sy-subrc
RAISING
 cx_sy_arithmetic_error
 cx_sy_conversion_error.
INCLUDE rs_bct_bupa_form_valid_to.
ENDFORM. "BPDATETO
FORM compute_GENDER
 CHANGING
 RESULT TYPE tys_TG_1_full-GENDER
 RETURNCODE LIKE sy-subrc
 ABORT LIKE sy-subrc
RAISING
 cx_sy_arithmetic_error
 cx_sy_conversion_error.
INCLUDE rs_bct_bupa_form_gender.
ENDFORM. "GENDER
FORM compute_GN_PAR_SSY
 CHANGING
 RESULT TYPE tys_TG_1_full-GN_PAR_SSY
 RETURNCODE LIKE sy-subrc
 ABORT LIKE sy-subrc
RAISING
 cx_sy_arithmetic_error
 cx_sy_conversion_error.
INCLUDE rs_bct_bupa_form_gn_par_ssy.
ENDFORM. "GN_PAR_SSY
$$ end of 2nd part global - insert your code only before this line *
 CLASS routine IMPLEMENTATION
CLASS lcl_transform IMPLEMENTATION.
METHOD compute_0GENDER.
IMPORTING
 request type rsrequest
 datapackid type rsdatapid
 SOURCE_FIELDS-XSEXM TYPE C LENGTH 000001
 SOURCE_FIELDS-XSEXF TYPE C LENGTH 000001
 SOURCE_FIELDS-XSEXU TYPE C LENGTH 000001
 EXPORTING
 RESULT type tys_TG_1-GENDER
 DATA:
 MONITOR_REC TYPE rsmonitor.
*$*$ begin of routine - insert your code only below this line *-*
Data:
 l_s_error_log type rssm_s_errorlog_int,
 l_subrc type sy-tabix,
 l_abort type sy-tabix,
 ls_monitor TYPE rsmonitor,
 ls_monitor_recno TYPE rsmonitors.
REFRESH:
monitor,
monitor_recno.
Migrated transfer rule call
Perform compute_GENDER
 CHANGING
 RESULT
 l_subrc
 l_abort.
*-- Convert Messages in Transformation format
 LOOP AT G_T_ERRORLOG INTO l_s_error_log.
 move-CORRESPONDING l_s_error_log to MONITOR_REC.
 append monitor_rec to MONITOR.
 ENDLOOP.
 IF l_subrc <> 0.
 RAISE EXCEPTION TYPE cx_rsrout_skip_val.
 ENDIF.
 IF l_abort <> 0.
 RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
 ENDIF.
$$ end of routine - insert your code only before this line -
ENDMETHOD. "compute_0GENDER
 Method invert_0GENDER
 This subroutine needs to be implemented only for direct access
 (for better performance) and for the Report/Report Interface
 (drill through).
 The inverse routine should transform a projection and
 a selection for the target to a projection and a selection
 for the source, respectively.
 If the implementation remains empty all fields are filled and
 all values are selected.
METHOD invert_0GENDER.
$$ begin of inverse routine - insert your code only below this line-
... "insert your code here
$$ end of inverse routine - insert your code only before this line -
ENDMETHOD. "invert_0GENDER
ENDCLASS. "routine IMPLEMENTATION
let me know how to correct the above code.
thanks

Hi,
the field tran_structure is no more available. The name changed to source_fields. Additionally there is no datapak available. It is now source_fields_table. You might need to use field symbols to access the fields.
regards
Siggi

PSD files will not print from Photoshop CS4 (previously posted in Acrobat printing and prepress)

My questions are: Does the PSD file have the printer information encoded?
Also why has this just started to show up? My wife has work successfully under the same conditions, files moved and printed on different printers, with no problems in the past.
I (we) have been struggling with a recent problem trying to print PSD files from Photoshop CS4. (Vista 32 bit, Epson 3880 networked) When trying to print certain, but not all, PSD files I get the message: "Before you can perform printer-related tasks such as page setup or printing a document, you need to install a printer." I have been in contact with Adobe support about the issue but with little in the way of positive results. I was referred to a kb link: http://kb2.adobe.com/cps/409/kb409119.html Tried all that to no avail. (The first suggestion is absurd to the point of making me wonder what process is used to construct the kbs. You cannot open the print menu when you get this message so....?)
Other solutions are not acceptable for the work my wife is doing, editing high quality photographs for an exhibition with test prints and so on. We are under intense time pressue with four shows coming up in a very short time. The final solution offered is that CS5 has solved all of this. Hum? interesting. No comment except new program, new problems so not a real solution for us.
In searching the web about this problem I have come across many other people with the same problem working from different platforms and even different Adobe products. I noticed that the MAC OS seemed to cause the same problem and that there was a problem with Reader and Acrobat. In every case the problem is never solved by Adobe or anyone else and users find some "workaround". I too have found what we hope is a workaround in our contiued travels on the blogosphere, on flickr http://www.flickr.com/groups/wellington/discuss/72157621548183001/ as "...a nasty, nasty solution" but we skipped the flatten part and the GIMP part and resave the PSD under a different name.
Adobe does seem supportive but not that interested (CS4 right) but I would like to find a real solution and I think many people would benefit from it.
Anyway what I have found is that the PSD files that will not print have been printed on another printer at some time in the past. In my case the Printer was an Epson Artisan A50. The printer we are using now is the Epson Stylus Pro 3880. Even when trying to print wirelessly to the 3880 from the laptop (Was Vista, now Windows 7) that was used to edit and print with the A50, (USB connection) we saw the same error. So it seems that the printer information is somehow embedded in the PSD file (also mentioned in a Blog) and is keeping PS from seeing the printer because the same printer is not there.
Has anybody already found the fix?
I know this is a long post but I have been working on this problem and have heard all of the pat and frankly useless answers and workarounds. Can we find a solution and fix the problem?

Just a few examples, since you ask:
Dr Craig wrote:
…The first suggestion is absurd to the point of making me wonder what process is used to construct the kbs…
…Other solutions are not acceptable…
…The final solution offered is that CS5 has solved all of this. Hum? interesting. No comment except new program, new problems so not a real solution for us…
…In every case the problem is never solved by Adobe or anyone else and users find some "workaround"…
"...a nasty, nasty solution"…
…Adobe does seem supportive but not that interested (CS4 right)… b
…I have been working on this problem and have heard all of the pat and frankly useless answers and workarounds…
That attitude, Dr. Craig. Plus the verbosity you unconscionably inflicted on your fellow forum users.
Cheers.
Wo Tai Lao Le
我太老了       (Not posting as a scientist here
                           but as a Photoshop user
                           so I'll forego listing any unrelated academic titles.)

Shopping cart creation category dropdown selecting the most used category

Hi SRM gurus,
While creating a shopping cart one of our most used category gets selected by default before we start doing anything.
Everytime we have to change the category.
Is there a way that will become blank and we can select from the dropdown or the find list.
Kindly suggest.
We are using SRM component version 4.0, SRM server 5.0, our patch level 0008.
Thx. & reg.,
Sridhar.

Hi
Yes.. This was happening with us when we used SRM 4.0 version.
We have used an BADI Implementation to resolve this issue.
The BADI name is BBP_F4_READ_ON_EXIT 
For Product category -> Product category (attr. WGR, PRCAT) GET_CATEGORY Method, you need to go ahead.
Read the documenation of this BADI and you will get the problem resolved after implementing the same.
Here is the documentation
BBP_F4_READ_ON_EXIT
Short Text
Restrict the Display in Input Helps and Search Helps
You can use the Business Add-In (BAdI) BBP_F4_READ_ON_EXIT to restrict (or augment) the list of values and favorites that are output in the input and search helps. You can only process data elements for which input helps exist on HTML templates. The following three BAdIs are also available:
BBP_F4_READ_ON_ENTRY
Use this BAdI if you do not just want to restrict the favorites and values list but also want to select this yourself.
BBP_F4_MEM_UPDATE
BBP_F4_SAVE_DB
The following three modules are used to process the values per data element:
BBP_GET_<data element>_F4
Supplies a list of all values and user-specific favorites. You can influence how this module works using BAdI BBP_F4_READ_ON_ENTRY and BBP_F4_READ_ON_EXIT.
BBP_UPD_<data element>_FAV
Updates the favorites in internal function group storage. You can influence how this module works using BAdI BBP_F4_MEM_UPDATE.
BBP_SET_<data element>_FAV
Writes the current favorites to the database. You can influence how this module behaves using BAdI BBP_F4_SAV_DB.
Use
Only implement this BAdI and only program the appropriate method if you want to restrict or augment the value set of standard selection.
If you determine favorites using a BAdI, the standard modules do not process the favorites further. Warning: If, deviating from standard selection, you determine the list of favorites yourself using a BAdI, you have to temporarily store the favorites in the methods of the BAdIs and carry out final saving to the database yourself.
Standard settings
If data is added via the methods, no check of this data occurs. The check has to occur in the methods themselves.
The interfaces of the methods of the BAdI are (almost) always the same:
IV_LANGUAGE
Language for determination of the texts
IV_USER
User for which the values are requested
ET_<data element>_LIST
The list of valid values changed by you
EV_X_FAV_PROCESSED
Use "X" to stipulate that you have filled the favorites list. Only present if favorites table exists for relevant data element.
ET_<data element>_FAVOURITES
Changed favorites list for user IV_USER. Only exists if favorites table exists for relevant data element.
The methods have to fill the structures of the transfer tables completely. Incompletely filled structures can cause followup errors and unforseen consequences.
Activities
Reading of value lists and favorites using function module BBP_GET_<data element>_F4 occurs as follows:
1. First the BAdI BBP_F4_READ_ON_ENTRY is called. It is possible to fill the input list (and favorites) with default values.
a) In the case of default values, exactly these values are returned to the initiator. No further processing or check occurs and the module is exited.
b) If no default values exist, the standard selection is carried out.
2. Before the values are transferred externally you can restrict or augment the number of hits using the BAdI BBP_F4_READ_ON_EXIT. You can therefore delete entries from or add entries to the input list or favorites list.
3. BAdI BBP_F4_READ_ON_EXIT provides an individual method for each data element for which an input help and/or favorites table exists. These are listed below.
If you use this method, you need to indicate processing using the parameter EV_X_LIST_PROCESSED or EV_X_FAV_PROCESSED. Otherwise the selection is lost.
List of available methods per data element in BBP_F4_READ_ON_EXIT:
Field/Data element Method
Currency GET_CURRENCY
Region GET_REGION
Country GET_COUNTRY
Language GET_LANGUAGE
Industry GET_INDUSTRY
Academic title GET_ACADEMIC
Time zones GET_TIMEZONE
Procurement cards GET_PCARD
Legal forms GET_LEGAL
Format for name format GET_NAMEFORM
Quality management systems GET_QMSYSTEM
Fixed values GET_DOMVALUE
Form of address texts GET_TITLEKEY
Units of measure GET_UNIT
Bank data GET_BANKINFO
Tax number types GET_TAXNUMT
Tax numbers per country GET_TAXTYPE
Tax groups per tax type GET_TAXGROUP
Terms of payment GET_PAYMTERM
RFC destinations GET_RFC_LOGS
Logical systems GET_LOGSYS
Tax codes GET_TAXCODE
Catalogs (attribute CAT) GET_CATALOG
Roles (attribute ROLE) GET_ROLE
Account assignment categories (attribute KNT) GET_KNT_ATTR
Purchasing organizations (from PdOrg) GET_PURCHORG
Purchasing organizations (per company) GET_PORGCOMP
Purchasing group (from PdOrg) GET_PURCHGRP
Purchasing group (per company) GET_PGRPCOMP
Product category (attr. WGR, PRCAT) GET_CATEGORY
Products GET_PRODUCT
Goods recipient plant (attr. REQUESTER) GET_GRCPLANT
Goods recipient user (attr. REQUESTER) GET_GRCUSER
Requester (attribute REQUESTER) GET_BOBUSER
Cost centers (attribute CNT) GET_COSTCENT
Asset classes (attribute ANK) GET_ASSETCL
Assets (attribute AN1) GET_ASSETNO
Asset subnumbers (attribute AN2) ET_ASSETSUB
Network (attribute NET) GET_NETWORK
WBS element (attribute PRO) GET_WBSELEM
Order (attribute ANR) GET_ORDERNO
Customer order (attribute AUN) GET_SDDOC
Customer order item (attribute APO) GET_SDDOCPOS
Document type (attribute BSA) GET_DOCTYPE
Transaction type (attribute TEND_TYPE) GET_TENDTYPE
Incase you face any problems, do let me know.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Salutation in mail forms.

Dear CRM gurus.
We are facing the following issue. When we want to create a mail form and when we want to create text different text elements using different salutation, we cannot use the conditions properly.
We cannot use basic conditions for distinguishing the salutation. Once we want to use salutation from the system field TITLE_LET (Salutation) when the fields is not empty even the field TITLE_MEDI (Title) is filled. Than we want to enter text element with salutation Mr. Mrs etc. when the field TITLE_LET (Salutation) is empty. But how we can tell the CRM that it should consider or not consider u201CEMPTYu201D field? And how to tell system that when the fields TITLE_LET (Salutation) and TITLE_MEDI (Title) are empty use the third possibility u2013 text elements with common salutation as u201CDear allu201D. Is it possible to use different way how to do this?
And what more, when we use field TITLE_LET (Salutation) in the text element it happens that the system enter data from field TITLE_MEDI (Title) instead.
Thank you for any hints.
Best regards,
Petr

Hi Petr,
I've created a custom function module that creates the salutation depending on the language and country. I.e. in Germany only the academic title Dr. or Prof. are part of the salutation. In Austria every academic title i.e. "Ing." must be added. This function module is called using the BAdI CRM_IM_ADD_DATA_BADI.
Best regards
Gregor

E-Recruiting 6.0: Name Field

Hi Experts,
I have the following questions as regards to 'name' field and would appreciate your help:
1) I understand the name fields (first name and last name) cannot be customised. But does E-Recruiting support the addition of middle name? I can configure under Business Partner to add in the Middle name, but it did not display on the E-Recruiting screen or R/3 BP transaction. I am not sure whether standard E-Recruiting does not support it or I have not configure correctly.
2) What is the table name which stores the name of a candidate and the applicant objecet number? I can see the name of the candidate in transaction BP, but i do not know where to find the applicant number. I need the information to for tracing and troubleshooting purposes.
Many thanks,
William

Hello William,
with e-recruiting 600 support package 10 or 11 e-recruiting supports middle name, 2nd academic title and name prefixes in the web dynpro frontend as standard fields for candidates. Unfortunately it seems SAP is no longer adding such stuff to the BSP frontend. In transaction BP you should be able to see these fields if noone changed BP. But the fields are only visible when filled so you might have to change to edit mode to click this small button with the plus.
Personal data of candidates name, birthdate, gender, titles are stored in the standard business partner tables BUT000 and following. Address is saved in the tables of the central address service but needs an entry in IT5110. That's why adding an address in BP won't work while changing is possible.
To get the differnt keys which are used for the candidate I usually start from BP as I have a name. I simply use the sear help of BP to get the BP number. Then it's all about HRP1001 which stores all object relations. As BP is an external object from HR view (as is the User) you put the BP into SCLAS and number into SOBID field (dont forget leading zeros here) and you can get the CP number. With the CP number you can get the User and the candidate (NA) number. From the candidate you can get applications (ND) and candidacies (NE) and so on.
Best Regards
Roman Weise

Error Message ORA-31043: Element 'person' not globally defined in schema

Hello All,
We have registered 2 xsd documents as follows..
DECLARE
 lc_test_xsd CLOB;
BEGIN
 lc_test_xsd := '<?xml version="1.0" encoding="UTF-8"?>
<schema
 xmlns="http://www.w3.org/2001/XMLSchema"
 xmlns:tns="http://www.xyz.com/cicat/types/basictypes/2/0"
 targetNamespace="http://www.xyz.com/cicat/types/basictypes/2/0"
 version="2.0">
 <simpleType name="LastNamePrefix">
 <annotation>
 <documentation>
 Additional word to last name (name prefix) corresponding to SAP HR Core
 Table T535N; V.
 </documentation>
 </annotation>
 <restriction base="tns:String255" />
 </simpleType>
 <simpleType name="CountryID">
 <annotation>
 <documentation>
 Codes for the representation of country names according to ISO 3166.
 </documentation>
 </annotation>
 <restriction base="string">
 <maxLength value="2" />
 </restriction>
 </simpleType>
 <simpleType name="LocationCode">
 <annotation>
 <documentation>
 Code of a location, e.g. Fe, Wa2 or Kor.
 </documentation>
 </annotation>
 <restriction base="string">
 <maxLength value="4" />
 </restriction>
 </simpleType>
 <simpleType name="GenderCode">
 <annotation>
 <documentation>
 Code of the gender: male, female, unknown. Unknown is used if the value is
 unknown or must not be stored due to legal restrictions.
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="male" />
 <enumeration value="female" />
 <enumeration value="unknown" />
 </restriction>
 </simpleType>
 <simpleType name="String255">
 <annotation>
 <documentation>
 String with 255 characters max
 </documentation>
 </annotation>
 <restriction base="string">
 <maxLength value="255" />
 <minLength value="1" />
 </restriction>
 </simpleType>
 <simpleType name="RB-CostCenter">
 <annotation>
 <documentation>
 Cost Center
 </documentation>
 </annotation>
 <restriction base="string">
 <minLength value="3" />
 <maxLength value="6" />
 </restriction>
 </simpleType>
 <simpleType name="OrgUnitName">
 <annotation>
 <documentation>
 Name of the Organizational Unit
 </documentation>
 </annotation>
 <restriction base="string">
 <minLength value="1" />
 <maxLength value="18" />
 </restriction>
 </simpleType>
 <complexType name="StringMCA">
 <annotation>
 <documentation>
 Multi Country String. Strings, which must be stored in ASCII code and
 country specific. The subelement ASCIIString contains the string encoded
 with ASCII. The subelement countrySpecificString allows country specific
 encoding.
 </documentation>
 </annotation>
 <sequence>
 <element name="asciiString" type="tns:String255" minOccurs="0" />
 <element name="countrySpecificString" type="tns:String255" />
 </sequence>
 </complexType>
 <simpleType name="OrgUnitID">
 <annotation>
 <documentation>
 ID of the Organizational Unit
 </documentation>
 </annotation>
 <restriction base="unsignedInt">
 <totalDigits value="8" />
 </restriction>
 </simpleType>
 <simpleType name="GlobalID">
 <annotation>
 <documentation>
 Global unique identifier of persons at xyz
 </documentation>
 </annotation>
 <restriction base="unsignedInt">
 <totalDigits value="8" />
 </restriction>
 </simpleType>
 <simpleType name="CiCatPersonID">
 <annotation>
 <documentation>
 CI-CAT Identifier of Persons (CiCat-PID). Unique identifier of a person
 in CI-CAT
 </documentation>
 </annotation>
 <restriction base="unsignedInt">
 <totalDigits value="20" />
 </restriction>
 </simpleType>
 <simpleType name="CiCatAccountID">
 <annotation>
 <documentation>
 CI-CAT Identifier of AD Accounts (CiCat-Ben-Sid). Unique identifier of
 AD Accounts in CI-CAT.
 </documentation>
 </annotation>
 <restriction base="unsignedInt">
 <totalDigits value="20" />
 </restriction>
 </simpleType>
 <simpleType name="PersonnelActionTypeCode">
 <annotation>
 <documentation>
 The operation that was performed on the person: entry, data change,
 re-entry (into company), exit (out of company)
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="entry" />
 <enumeration value="data change" />
 <enumeration value="re-entry" />
 <enumeration value="exit" />
 </restriction>
 </simpleType>
 <simpleType name="ContractStatus">
 <annotation>
 <documentation>
 Contract Status: active, inaktive, resigned, retired
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="retired">
 <annotation>
 <documentation>
 End of contract relationship because of retirement
 </documentation>
 </annotation>
 </enumeration>
 <enumeration value="resigned">
 <annotation>
 <documentation>
 End of contract because of quitting
 </documentation>
 </annotation>
 </enumeration>
 <enumeration value="inactive">
 <annotation>
 <documentation>
 Incactive contract relationship, e.g. motherhood, suspension
 </documentation>
 </annotation>
 </enumeration>
 <enumeration value="active">
 <annotation>
 <documentation>
 Normal contract status
 </documentation>
 </annotation>
 </enumeration>
 <enumeration value="deleted">
 <annotation>
 <documentation>
 Contract physically deleted in the source system
 </documentation>
 </annotation>
 </enumeration>
 </restriction>
 </simpleType>
 <simpleType name="KnownAssociateCode">
 <annotation>
 <documentation>
 Describes status of person to xyz: internal/external/fixed-term
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="External" />
 <enumeration value="Internal" />
 <enumeration value="Fixed Term" />
 <enumeration value="unknown" />
 </restriction>
 </simpleType>
 <simpleType name="AssociateCode">
 <annotation>
 <documentation>
 Describes status of person to xyz: union of known values plus free string
 for not yet known types
 </documentation>
 </annotation>
 <union memberTypes="tns:KnownAssociateCode string" />
 </simpleType>
 <simpleType name="KnownExternalRelationType">
 <annotation>
 <documentation>
 Describes relation (contract relation) of external person to xyz:
 contractor/customer/supplier/subsidiary/selfregistered
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="Contractor" />
 <enumeration value="Customer" />
 <enumeration value="Supplier" />
 <enumeration value="Subsidiary" />
 <enumeration value="Selfregistered" />
 <enumeration value="unknown" />
 </restriction>
 </simpleType>
 <simpleType name="ExternalRelationType">
 <union memberTypes="tns:KnownExternalRelationType string" />
 </simpleType>
 <simpleType name="ValidityState">
 <annotation>
 <documentation>
 If an attribute was taken over by an authoritative source such as HR-MDS or
 WOM. Set to "Valid" to indicate that the value was taken over from the
 source and is therefore valid. Set to "Invalid" if the source indicates the
 value is no longer value, e.g. because it got deleted. Otherwise set to
 "Unknown", e.g. when the value was entered manually.
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="Valid" />
 <enumeration value="Invalid" />
 <enumeration value="Unknown" />
 </restriction>
 </simpleType>
 <complexType name="HrPersonnelId">
 <sequence>
 <element name="hrSourceSystem">
 <annotation>
 <documentation>
 Name of HR source system
 </documentation>
 </annotation>
 <simpleType>
 <restriction base="string">
 <minLength value="1" />
 <maxLength value="20" />
 </restriction>
 </simpleType>
 </element>
 <element name="hrPersonnelId">
 <annotation>
 <documentation>
 ID of person in HR source system
 </documentation>
 </annotation>
 <simpleType>
 <restriction base="string">
 <minLength value="1" />
 <maxLength value="20" />
 </restriction>
 </simpleType>
 </element>
 </sequence>
 </complexType>
 <complexType name="AccountType">
 <annotation>
 <documentation>
 Types of Accounts: Three main categories are known: Person, resource or
 service account. A person account represents a single natural person. A
 resource account represents a resource such as a printer, a computer or a
 meeting room. Service Accounts represent everything else. The can be used
 for example for technical users or group accounts. Both resource and service
 accounts have an owner that is responsible for them. Each account type has
 subtypes for further categorization.
 </documentation>
 </annotation>
 <choice>
 <element name="personAccount" type="tns:PersonAccountType" />
 <element name="resourceAccount" type="tns:ResourceAccountType" />
 <element name="serviceAccount" type="tns:ServiceAccountType" />
 </choice>
 </complexType>
 <simpleType name="KnownPersonAccountType">
 <annotation>
 <documentation>
 Pre-defined types of Person Accounts
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="Office" />
 <enumeration value="Admin" />
 <enumeration value="Test" />
 <enumeration value="unknown" />
 </restriction>
 </simpleType>
 <simpleType name="PersonAccountType">
 <union memberTypes="tns:KnownPersonAccountType string" />
 </simpleType>
 <simpleType name="KnownResourceAccountType">
 <annotation>
 <documentation>
 Pre-defined types of Resource Accounts
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="Room" />
 <enumeration value="PC" />
 <enumeration value="Printer" />
 <enumeration value="unknown" />
 </restriction>
 </simpleType>
 <simpleType name="ResourceAccountType">
 <union memberTypes="tns:KnownResourceAccountType string" />
 </simpleType>
 <simpleType name="KnownServiceAccountType">
 <annotation>
 <documentation>
 Pre-defined Types of Service Accounts
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="Group" />
 <enumeration value="Machine" />
 <enumeration value="Support" />
 <enumeration value="System" />
 <enumeration value="unknown" />
 </restriction>
 </simpleType>
 <simpleType name="ServiceAccountType">
 <union memberTypes="tns:KnownServiceAccountType string" />
 </simpleType>
 <simpleType name="ActionType">
 <annotation>
 <documentation>
 Defines the action that was performed on the object.
 </documentation>
 </annotation>
 <restriction base="string">
 <enumeration value="Create" />
 <enumeration value="Update" />
 <enumeration value="Delete" />
 </restriction>
 </simpleType>
 <simpleType name="LegalEntityId">
 <annotation>
 <documentation>
 ID of a legal entity
 </documentation>
 </annotation>
 <restriction base="unsignedInt">
 <totalDigits value="8" />
 </restriction>
 </simpleType>
</schema>
 DBMS_XMLSCHEMA.REGISTERSCHEMA (schemaurl => 'BasicTypes.xsd',
 schemadoc => lc_test_xsd);
DBMS_OUTPUT.PUT_LINE('BasicTypes.xsd registration successfully completed');
EXCEPTION WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('BasicTypes.xsd registration failed '||SQLERRM);
END;
/

2nd xsd..
-- register PersonTypes.xsd schema
DECLARE
lc_person_xsd CLOB;
BEGIN
 lc_person_xsd
 := '<?xml version="1.0" encoding="UTF-8"?>


<schema
 xmlns="http://www.w3.org/2001/XMLSchema"
 xmlns:tns="http://www.xyz.com/cicat/types/persontypes/2/0"
 xmlns:basic="http://www.xyz.com/cicat/types/basictypes/2/0"
 targetNamespace="http://www.xyz.com/cicat/types/persontypes/2/0"
 version="2.0">
 <import namespace="http://www.xyz.com/cicat/types/basictypes/2/0" schemaLocation="BasicTypes.xsd"/>
 <complexType name="ADAccount">
 <annotation>
 <documentation>
 Active directory account of a person (also known as NT or Windows account)
 </documentation>
 </annotation>
 <sequence>
 <element name="cicatAccountId" type="basic:CiCatAccountID">
 <annotation>
 <documentation>
 CICAT internal ID of account (CI-CAT Ben SID)
 </documentation>
 </annotation>
 </element>
 <element name="domain" type="basic:String255">
 <annotation>
 <documentation>
 NT domain of the userID, e.g. "de", "emea"
 </documentation>
 </annotation>
 </element>
 <element name="userID" type="basic:String255">
 <annotation>
 <documentation>
 NT userID e.g. "xyz5mum" without domain (NT-SID)
 </documentation>
 </annotation>
 </element>
 <element name="guid" type="basic:String255">
 <annotation>
 <documentation>
 Active Directory GUID of account.
 </documentation>
 </annotation>
 </element>
 <element name="isMasterAccount" type="boolean"
 default="false" minOccurs="0">
 <annotation>
 <documentation>
 A person can have several accounts. One of them is marked as the
 master account. The master account is the account which is mainly
 used by the user.
 </documentation>
 </annotation>
 </element>
 <element name="accountType" type="basic:AccountType">
 <annotation>
 <documentation>
 Types of Accounts: Three main categories are known: Person, resource
 or service account. A person account represents a single natural
 person. A resource account represents a resource such as a printer,
 a computer or a meeting room. Service Accounts represent everything
 else. The can be used for example for technical users or group
 accounts. Both resource and service accounts have an owner that is
 responsible for them. Each account type has subtypes for further
 categorization.
 </documentation>
 </annotation>
 </element>
 </sequence>
 </complexType>
 <complexType name="Person">
 <annotation>
 <documentation>
 All attributes a CI-CAT person record can contain
 </documentation>
 </annotation>
 <sequence>
 <element name="globalID" type="basic:GlobalID" minOccurs="0">
 <annotation>
 <documentation>
 Globally unique identifier of a person at xyz. This ID is defined
 by HR MDS.
 </documentation>
 </annotation>
 </element>
 <element name="cicatPID" type="basic:CiCatPersonID">
 <annotation>
 <documentation>
 Unique identifier of person in CI-CAT.
 </documentation>
 </annotation>
 </element>
 <element name="hrPersonnelId" type="basic:HrPersonnelId" minOccurs="0">
 <annotation>
 <documentation>
 Personnel ID of person in an HR system. The personnel ID is unique
 throughout one system. But different systems can use the same ID.
 </documentation>
 </annotation>
 </element>
 <element name="title" type="basic:String255"
 minOccurs="0">
 <annotation>
 <documentation>
 Title of the person. In some countries and HR-MDS this field is used
 for the academic title. In other countries it is used for the job
 title.
 </documentation>
 </annotation>
 </element>
 <element name="firstName" type="basic:StringMCA">
 <annotation>
 <documentation>
 First name of the person
 </documentation>
 </annotation>
 </element>
 <element name="middleName" type="basic:StringMCA" minOccurs="0">
 <annotation>
 <documentation>
 Middle name(s) of the person
 </documentation>
 </annotation>
 </element>
 <element name="lastNameAddOn" type="basic:String255"
 minOccurs="0">
 <annotation>
 <documentation>
 Additional word to surname (name prefix)
 corresponding to SAP HR Core Table T535N; V.
 </documentation>
 </annotation>
 </element>
 <element name="lastName" type="basic:StringMCA">
 <annotation>
 <documentation>
 Last names of the person.
 </documentation>
 </annotation>
 </element>
 <element name="displayName" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 Display name of the person. This attribute is calculated from the
 name, the department. In case of external users it also contains
 an external flag and the name of the company. This field is
 calculated by CI-CAT.
 </documentation>
 </annotation>
 </element>
 <element name="gender" type="basic:GenderCode" minOccurs="0">
 <annotation>
 <documentation>
 Gender of the person
 </documentation>
 </annotation>
 </element>
 <element name="orgUnitID" type="basic:OrgUnitID" minOccurs="0">
 <annotation>
 <documentation>
 ID of Organization unit (determined by C/AOO). This ID is taken over
 from WOM.
 </documentation>
 </annotation>
 </element>
 <element name="orgUnitIDValidity" type="basic:ValidityState" minOccurs="0">
 <annotation>
 <documentation>
 Defines if the attribute orgUnitID was validated by an authoritative
 source. The default value is "Unknown".
 VALID:
 - orgUnitID is linked with WOM reference and orgUnitID is active in WOM
 - orgUnitID is linked with Exception Organization list maintained in
 CI-CAT by C/AOO. orgUnitID is active in with Exception Organization list
 INVALID:
 - orgUnitID is linked with WOM reference and orgUnitID is inactive in WOM
 - orgUnitID is linked with Exception Organization list maintained in CI-CAT
 by C/AOO. orgUnitID is inactive in with Exception Organization list
 UNKNOWN:
 - orgUnitID is not linked with WOM reference or Exception Organization
 list. Active state of the department is not known.
 </documentation>
 </annotation>
 </element>
 <element name="orgUnitName" type="basic:OrgUnitName">
 <annotation>
 <documentation>
 Unit Code (determined by C/AOO) of the organizational office, e.g.
 Department, group, Project.
 </documentation>
 </annotation>
 </element>
 <element name="costCenter" type="basic:RB-CostCenter">
 <annotation>
 <documentation>
 Cost center the person is assigned to.
 </documentation>
 </annotation>
 </element>
 <element name="costCenterValidity" type="basic:ValidityState" minOccurs="0">
 <annotation>
 <documentation>
 Defines if the attribute costCenter was validated by an authoritative
 source. The default value is "Unknown".
 </documentation>
 </annotation>
 </element>
 <element name="email" type="basic:String255"
 minOccurs="0">
 <annotation>
 <documentation>
 Primary email of person
 </documentation>
 </annotation>
 </element>
 <element name="legalEntity" type="basic:LegalEntityId" minOccurs="0">
 <annotation>
 <documentation>
 ID of a legalEntity. Legal Entity List will be
 retrieved from CI-CAT.
 </documentation>
 </annotation>
 </element>
 <element name="officeLocation" type="basic:LocationCode" minOccurs="0">
 <annotation>
 <documentation>
 The office location where the person is currently working,
 e.g. Fe, Kor, Wa2. Maintained in CI-CAT.
 </documentation>
 </annotation>
 </element>
 <element name="maintenanceLocation" type="basic:LocationCode" minOccurs="0">
 <annotation>
 <documentation>
 The location of the HR department which maintains the person, taken from HR-MDS.
 </documentation>
 </annotation>
 </element>
 <element name="building" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 Building free-from data
 </documentation>
 </annotation>
 </element>
 <element name="room" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 Room (Section, floor and room number)
 </documentation>
 </annotation>
 </element>
 <element name="externalCompany" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 For Externals: Name of the external company.
 </documentation>
 </annotation>
 </element>
 <element name="externalCompanyLocation" type="basic:LocationCode" minOccurs="0">
 <annotation>
 <documentation>
 For Externals: The location of the external company.
 </documentation>
 </annotation>
 </element>
 <element name="personnelActionType" type="basic:PersonnelActionTypeCode" minOccurs="0">
 <annotation>
 <documentation>
 Defines the action type used in SAP HR systems,e.g. Hiring (entry);
 Organizational reasignment; Transfer; Change in pay;
 early retirement / retirement; leaving; Re-entry into company
 </documentation>
 </annotation>
 </element>
 <element name="statusOfContract" type="basic:ContractStatus">
 <annotation>
 <documentation>
 Status of current occupation, e.g. active; inactive; resigned; retired
 </documentation>
 </annotation>
 </element>
 <element name="xyzGroupAssociate" type="basic:AssociateCode">
 <annotation>
 <documentation>
 Indicates whether person is xyz Group associate or external
 according to respective regulations : external; internal
 </documentation>
 </annotation>
 </element>
 <element name="externalRelationToxyz" type="basic:ExternalRelationType"
 minOccurs="0" maxOccurs="unbounded">
 <annotation>
 <documentation>
 Describes for persons of type xyzGroupAssociate = external the
 relationship to xyz, e.g. customer, subsidiary, ...
 Persons can be in more than one relation to xyz.
 </documentation>
 </annotation>
 </element>
 <element name="phone" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 Phone Number
 </documentation>
 </annotation>
 </element>
 <element name="otherPhone" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 "Business 2/Other Telephone" ist ein multivalue field which can be
 filled with additional phone numbers (canonical format).
 </documentation>
 </annotation>
 </element>
 <element name="mobile" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>
 Mobile Phone Number
 </documentation>
 </annotation>
 </element>
 <element name="paperFax" type="basic:String255" minOccurs="0" />
 <element name="electronicFax" type="basic:String255" minOccurs="0" />
 <element name="ipPhone" type="basic:String255" minOccurs="0">
 <annotation>
 <documentation>IP Phone Number</documentation>
 </annotation>
 </element>
 <element name="lastModified" type="dateTime">
 <annotation>
 <documentation>
 last Time person was modified in CI-CAT
 </documentation>
 </annotation>
 </element>
 <element name="lastModifyingUser" type="basic:String255">
 <annotation>
 <documentation>
 Last person, who modified person in CI-CAT. Can be a CI-CAT system
 user, e.g. user to connect CI-CAT to WOM.
 </documentation>
 </annotation>
 </element>
 <element name="assistant" type="basic:GlobalID" minOccurs="0">
 <annotation>
 <documentation>
 Assistant of person. Reference to assistant vie
 globalId
 </documentation>
 </annotation>
 </element>
 <element name="activeDirectoryAccount" type="tns:ADAccount"
 maxOccurs="unbounded" minOccurs="0">
 <annotation>
 <documentation>
 List of Active Directory accounts of the user.
 To indicate that a user is deleted, the list of
 AD accounts is empty.
 </documentation>
 </annotation>
 </element>
 </sequence>
 <attribute name="action" type="basic:ActionType" use="required"/>
 </complexType>
 <element name="person" type="tns:Person"/>
</schema>
 DBMS_XMLSCHEMA.REGISTERSCHEMA (schemaurl => 'PersonTypes.xsd',
 schemadoc => lc_person_xsd);
DBMS_OUTPUT.PUT_LINE('PersonTypes.xsd registration successfully completed');
EXCEPTION WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('PersonTypes.xsd registration failed '||SQLERRM);
END;

Candidate Data -- E-Recruiting

In Create Internal Applications / External Applications service (Recruiter role) in the Candidate Data group
there is title / second title field
What is purpose of this field, what values are typically used and where do you make the settings.
I check in IMG there is no table to set for title / second title
How others use it?

Hello,
These are academic titles/qualifications granted to students after pursuing university education. After completing your Bachelor's degree you will get academic title 'Bachelor' or 'Doctor' title after studying your Ph.D. Its possible to have multiple titles and this is why there are 2 seperate fields in my opinion so you can enter at least 2 if you have them.
The values are configured under spro in Cross-Application Components > SAP Business Partner > Business Partner > Persons > Name Components > Maintain Academic Titles. They are saved in table TSAD2. When assigned to a candidate they are saved in the BUT000 against the BP for the candidate in fields TITLE_ACA1 and TITLE_ACA2.
Regards,

USERS_GEN : Upload User from file

Does anyone knows where the field cournty is stocked and what is its role?
Thanks

Hello, here is the snippet of the information of this transaction
Option 1: Upload Users from File (ASCII)
Prerequisite
The data fields for a user are in a row and are separated by a
semicolon. You can generate these files in MS Excel, for example, (save
the Excel sheet as file type CSV). The order of the fields is critical.
Example
o   D030456;Smith;50000105;[email protected];de
o   C00213445;Doe;50000106;[email protected];us
o   D23456;Moser;50010203;[email protected];dk
Note
In the menu under Goto -> Define Separator, you can determine if a
semicolon or a comma is to be accepted as a separator.
If all the data in the file is not accessible, default values are used
for the missing data. If the file contains an e-mail address, the system
generates a password and sends it via e-mail to the user. If the file
has not e-mail address, you are prompted to specify an initial password
for all users.
You must specify the technical key for the fields Academic title, Form
of address, Manager indicator, Role and Country.
o   You can find the system keys for the academic title in field
    TITLE_KEY of table TSAD2.
o   You can find the system keys for the address text in field TITLE of
    table TSAD3T.
o   If the user is to be a manager, you check the field Manager
    indicator.
o   If you are assigning a role for a user, the file must contain the
    technical name of the role. You should check in advance in
    Transaction PFCG if the role actually exists.
Regards, Luciano.

CRM form of address

Hi,
I'm in CRM 2007 6.0, trying to figure out what was the standard set of "form of address" that CRM delivered. This is because it has been customized 100% previously.
Please comment.

SAP delivers some standard Forms of Address, usually four key entries (and their corresponding translated entries).
Here's a typical extract of the Forms of Address table under Address Management/Business Address Services
Key    Title       Person   Org   Grp   Gender
0001      Ms.         X        X           2 Female
0002      Mr.          X        X           1 Male
0003      Company              X           Gender not known
0004      Dr.          X                    Gender not known
Take care as there are also special Forms that are maintained separately such as Academic Titles (6 entries), Name Prefixes (10 entries), Supplements (6 entries) and so on.

Occupation in ICCMP_BP_CP has no drop down or description

In the UI component ICCMP_BP_CP I added Occupation from the folder CONTACTPERSON to the view but it does not bring accross the description or the open input help.
I can put in the key but that is not good for the users.
The same view has Function & Academic Title where
label is A - F
key is G - I
description of key J - P
Is this configurable or require development?

in BSP_WD_CMPWB for ICCMP_BP_CP in my enhancement set I see the attribute STRUCT.OCCUPATION, I generated the Getter and Setter methods and M methods (similiar to STRUCT.TITLE_ACA1) but that did not resolve my issue in the UI.
Edited by: Glenn Michaels on Sep 23, 2009 4:34 AM

Academic Title

Similar Messages

Maybe you are looking for