Field DESC_LANGUAGE is not available in structure CRMT_ORDERADM_H_COM

Question

I get the following warning message when I create a CRM ticket from trx notif_create.
Field DESC_LANGUAGE is not available in structure CRMT_ORDERADM_H_COM (CRM_ORDER_MISC001)
I have been looking in notes, forums and google but no help.
Could someone point me the right direction how to fix this, since the user does not get the confirmation of the ticket beeing created nor the number of the ticket.
I have copied standard trasnacion SLFN to ZLFN with all its profiles and headers, and activated it in DNO_CUST04 y in SPPFCADM.
Please advise.

Answer 1

Hi I have too problem, but don't assigment SAP Component in Message Support SLFN.
What procedure in DNO_CUST04.
System: SP HP1
I Have follow note 824640.
See you cheklist:
Solution
For point 1: You cannot determine a new process type.
If you use an alternative process type instead of SLF1 (the default until Release 3.20) or SLFN (the default as of Release 4.00), this must be entered as follows:
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: PROCESS_TYPE
Enter the description: Message Type
Enter the field value: SLFN (SLFN is an example of a new process type)
Choose Save.
OK.
For point 2: An external IBase ID is to be used.
If you use a different external IBase ID instead of SOL_MAN_DATA_REP (the default), this must be entered as follows:
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: IBASE
Enter the description: External IBase ID
Enter the field value: EXT_IBASE (EXT_IBASE is an example of an external IBase ID)
Choose Save.
OK
For point 3: The contact person is not transferred/displayed.
When you create a Service Desk message, you specify a contact person, whom the system does not display in the message.
Quando vc cria uma mensagem, vc especifica uma pessoa de contato, o qual o sistema não mostra na mensagem.
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: NO_USER_CHECK
Enter the description: No Existence Check for User
Enter the field value: X
Choose Save.
OK
For point 4: Transaction NOTIF_CREATE does not start and the system issues no error message.
Call transaction SOLUTION_MANAGER or DSWP.
Choose: Edit -> Global settings.
Maintain your Solution Manager release accordingly:
3.1: Configuration guide 3.1 -> 4. Setting Up the SAP Solution Manager -> General Settings for the SAP Solution Manager
3.2: Implementation Guide -> Solution Manager -> Basic Settings -> SAP Solution Manager System -> Connection to SAP -> Assign User to Forward Service Desk Messages
OK
For point 5: There is no Service Desk - RFC connection for the Solution Manager.
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: RFCDEST_SOL_MANAGER
Enter the description: RFC connection for Solution Manager
Enter the field value: RFC connection from transaction SM59 or NONE for local system
Choose Save.
OK
For point 6: There are SAP components missing in transaction NOTIF_CREATE.
In transaction NOTIF_CREATE, no values are displayed for the components in the F4 help.
Call transaction SOLUTION_MANAGER or DSWP.
Choose: Edit -> Get SAP components
or start the program DSWP_GET_CSN_COMPONENTS.
Call transaction SE38.
Enter the program  DSWP_GET_CSN_COMPONENTS
Choose Execute (F8).
OK
For point 7: Separate/changed partner function for contact person and/or person responsible
When you use separate partner functions, you must enter the
following user settings:
Releases up to Release 3.10 / 3.20 (Support Package 15) or Release 4.00 (Support Package 10)
If you have a separate partner function for the contact person:
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: PARTNER_FCT_DESC_CREA
Enter the description: Separate Partner Function for Contact Person (CREA)
Enter the field value: Enter the value you used as an abbreviation when creating your partner function (see comment below).
Important: You must enter the field value in uppercase letters.
Choose Save.
OK
If you have a separate partner function for the person responsible:
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: PARTNER_FCT_DESC_PROC
Enter the description: Separate Partner Function for Person Resp (PROC)
Enter the field value: Enter the value you used as an abbreviation when creating your partner function (see comment below).
Important: You must enter the field value in uppercase letters.
Choose Save.
OK
Releases as of Release 3.20 (Support Package 16) or Release 4.00 (Support Package 11)
If you have a separate partner function for the contact person:
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: PARTNER_FCT_CREA
Enter the description: Separate Partner Function for Contact Person (CREA)
Enter the field value: Enter the partner function you used for the contact person (see comment below).
Important: You must enter the field value in uppercase letters.
Choose Save.
CHECK
Not used
If you have a separate partner function for the person responsible:
Call transaction DNO_CUST04.
Choose New Entries.
Enter the field name: PARTNER_FCT_PROC
Enter the description: Separate Partner Function for Person Resp (PROC)
Enter the field value: Enter the partner function you used for the person responsible (see comment below).
Important: You must enter the field value in uppercase letters.
Choose Save.
CHECK
Not used
Comment: To maintain or display your partner functions, use transaction CRMC_PARTNER_FCT or transaction SPRO -> SAP Reference IMG -> SAP Solution Manager: Implementation Guide -> SAP Solution Manager -> Scenario-Specific Settings -> Service Desk -> Partner Determination Procedure -> Define Partner Functions.
Important: Since these entries are language-dependent, you have to maintain or change all of the languages you use in your system.
For point 8: The short text is too long when you create a message.
When you create a Service Desk message in a component system (enter using Help -> Support Message), the short text is too long (60 places) and the system truncates it in the message overview (transaction CRM_DNO_MONITOR) and in the transaction for message processing (CRMD_ORDER).
See Note 838063.
CHECK
Not Used
For point 9: Generate IBase components automatically
As of Release 4.00 (Support Package 15)
To be able to generate IBase components automatically when you create or change systems in the SMSY, you have to create the following Customizing entry using transaction DNO_CUST04.
Enter the field name: IB_GEN_AUTO
Enter the description: Automatic IBase Generation
Enter the field value: Blank character or X
Blank character = Automatic generation is switched on
X = Automatic generation is switched off
Not used