Maintain Text

Hi All,
I want to maintain text in infotype 0102 grievances and i am also maintaining the same but i want to maintain 2 t0 3 different texts in the same entry will it be possile ?
Thanks
Giri

Hi
In the infoobect -> master data/texts select short,medium,long texts then u can maintain 3 different texts.
Siri

Similar Messages

Unable to view the message in PA30 maintain text in workflow

Hi All,
We have developed a workflow which gets triggered when ever a record gets created in PA30 infotype 0267.
At the time of record creation the user can maintain his comments in Goto=> Maintain text.
After the record gets created the workflow gets trigerred,
the record gets locked and a workitem appears in the users
inbox.
The user doubles clicks on the workitem and a decision screen appears. Using the objects and Attachments the user can vie the record and also the icon for maintain text.
my problem is that after the record gets locked I am not able to view the text maintained in the maintain text editor,
whereas after that record gets unlocked I am able to view the text.
Are there any settings via which we can view the text irrespective whether it is created at the time record is locked or not.
Thanks and Regards
Shraddha

Hi,
By looking at the word 'Maintain text', it looks to me that it doensn't make sense to have this option up when that particluar record is locked. Or there should be an option saying 'Display Text'.
Anyway, what is the purpose of the comments written by the creator of the record? is it only to facilitate the next approver to take his decision or Do you need this comment always attached with record for some proof?
If comment is only to facilitate the next approver to take his decison and not really required to be attached along with record, then may be you can do the following
1. Once the record gets created, the first workitem send it to creator only. In the description mention to add comment and click to continue to go for approval. So, when work item comes to creator he can add the comment using 'Create' option with workitem and this comment will be there as an attachment through out the workflow. So approver will also be able to see the comment.
2. If at all it is required to store these comments along with record, once the whole approval process gets over, in the last step write a method to extract the attachments from workflow container and assign aginst the record. We have FM's to extract attachments ( SAP_WAPI_GET_ATTACHMENTS) and also FMs to store against an object (ARCHIV_CREATE_TABLE,ARCHIV_CREATE_FILE).
Hope this helps you !!
Regards
Krishna Mohan

Maintain Text in Different Language

Hi PS Expert,
I have query for maintaining text in multiple language, let me elaborate my query..
I created std project having all WBS element & maintain WBS Text ( description) in English lanuage.Now my client prefers that if a person in other country log into SAP in German language then he should see all description in German language.
I have one solution that log into SAP in German Language & maintain all text again in German language. This will be just repeatition of the work what I did in English language.Client wants to maintain all text in 6 language & I have to repeat the same work 6 times.
If you have come across such issue , please tell me about your solution.
Regards,
Ashok Sangal

Hi Ashok
Activate business function OPS_PS_CL1
Multi language support has to be activated fro the Object ML(IMG-->Project system-->activate multi language support)
when you create a new PS object , a new tab short text appears, in which you can maintain different language keys and description
so when ever user logs in different language then the description of PS object will appear in that language if it is maintained in short text tab
vijay

Maintain Text in Infotype 0041 via LSMW

Hi,
Has anyone had success loading text into Infotype 0041 via lsmw?
I am trying to create an lsmw to maintain text in infotpye 0041. I follow the route PA30, then when in IT0041 I go to edit and maintain text.
The problem is that I get a syntax error because the field I am trying to update is RSTXP-TDLINE which is a length 0 and format type string. LSMW won't accept string fields so in the generated program for the lsmw the line reads: "tdline_01(000000) type c,". This obviously doesn't pass the syntax check.
Any help greatly appreciated.
Regards,
Warren.

Hi
I just tried to create a LSMW in my DEV environment. I didnt get any error when recording. I entered the text in IT41 without any issue. What I am getting in the source code is:
RSTXP-TDLINE(01) Abcde TDLINE_01 ABAP Source Line
Am I missing what you are seeing?
Cheers
Pramod

Maintaining Text data for IT0102 in Ad Hoc Query

We use the "Maintain Text" function to store comments and additional data for Grievance information on IT0102. I need these comments to be included in a query for IT0102, however I only see the indicator for if text exists...there's no "field" to select to show the actual text - mainly because it's a note and not a field.
Any suggestions???

Hi,
you could make a custom field in your infoset for infotyp 0012. Then you could append code to this field and read the text with function module
HR_ECM_READ_TEXT_INFOTYPE into this field.
Regards Bernd

Where I can maintain Text symbols and Selection texts?

Hi there,
I need to maintain Text symbols and Selection texts of a program manually, but I can't find the tabs of Text symbols and Selection texts. My SAP is ECC6.0. Please help me with that...
Thanks a lot,
Bing

HELLO FRIEND
ALL THOSE REPLIES ARE A KIND OF HARD CODING....THOSE WILL WORK IN THAT CLIENT ALONE...IF YOU TRANSPORT THAT REPORT TO ANOTHER CLIENT THERE AGAIN YOU NEED TO MAINTAIN THE TEXT ELEMENTS AGAIN BY GOING TO THE MENU.....
BEST YOU CAN USE
INITIALIZATION EVENT
INTILIZE ALL THOSE TEXT ELEMENTS USING COMMENT SYNTAZ AND YOU CAN GIVE WHAT EVER THE TEXT ELEMENTS YOU WANT....
THIS IS THE BEST WAY OF PRACTICING AND THIS IS FOLLOWED IN REAL TIME TOO...
TRY THIS PLEASE.

How to maintain TEXT ID GROUP (table TTXERN)

Dear SAP,
I am having a problem on how to maintain TEXT ID GROUP (table TTXERN). Where is it configured and why after upgraded to ECC6, this table doesn't cover all data availbale in table TTXER?
Your expert advice is realy much appreciated. will give points for those who help me out this problem.
TQ
Regards,
Nazrul

You need to run the program SDTXT1AID, it will list all entries present in TTXER but missing in TTXERN.
It is very common to come across this issue during SAP upgrade.
You can refer to the std documentation of the program &/or Google it to find further details

Maintain text - transaction PA61

I have developed a transaction that creates an "Attendance" registration in HR. The same as transaction PA61 does !!
In my program I have used BAPI 'BAPI_PTMGRATTABS_MNGCREATION' and that works fine !
But in transaction PA61 you can create a text by choosing Edit ==> Maintain text.... So what I am looking for is a BAPI or a Function module that I can use to create this text from the transaction that I have developed !

When I have to upload some kind of a long text, I normally use function module SAVE_TEXT.
Important here is that ou use the correct import parameters. For parameter HEADER, you can find the necessary information in the text editor by going in the menu to GOTO- HEADER; the ones you are name, language, id (like 0001 for instance for sales text) and object (MVKE for sales text for instance).
You put the long text in an internal table and map it with table parameter LINES.
Hope this helps you,
Regards

Maintain text for all infotype

Hello,
Is someone knows why in some infotype the option "maintain text" is active and for others it isn't.
Can i active it for all infotype?
Thanks.
Edited by: marc frenay on Aug 20, 2009 12:43 PM

Hi,
You can change any standard Infotype text as per your requirment.Go the table view V_T582S & change the text for any infotype as per your requirement.
Snita

Maintain Text PA - Authorization issue?

Hi experts,
I'm having a problem when updating text in infotypes using "Maintain Text" (F9). Most user's SAP GUI block when trying t access the text window (after clicking Maintain text). SAP GUI just freeze (no message). It's the only time I have got an error like this.
Since some users are able to maintain text, do you think it could be an authorization issue?
Could you please show me which authorization object should be customized to let them to maintain text?
If you think is not an authorization issue, any idea?
I would really appreciate your help since I run out of ideas...
Thank you very much
Chema

Hi Dilek,
thank you for your help. SU53 shows a problem with authorizations for P_ORGXX (R, ,,,,) for people who can't maintain text, but it also show a problem with P_ORGINCON (R,,,,,,,) for people who can.
I know these two authorization object are related to infotype read/writing, but it is also related to maintain text feature?
MS Word comment seems a posible explanation, because since SAP GUI blocks should be any local configuration issue, but still all computers has the same version and instalation.
Thank you again for your help
Cheers,
Chema

Maintain text for Infotype 0015

Hi,
I want to upload the text to infotype 0015 via Maintain Text.
Can any one help me how to upload the text using export or macros.
Thanks & Regards,
Mohan

Hi Murali,
I haven't tried it.. but may be you can look at the logic in HR_READ_INFTY_NOTE & try to do the opposite.. ie something like
export ptext = text
to database pcl1(tx)
id key ignoring conversion errors.
You may have to read the infotype record first to get the key.. also remember to update the field ITXEX for eahc record.. otherwise, the text cannot be displayed via pa20/30..
~Suresh

"Maintain Text" (press F9) in LSMW

How to handle "Maintain Text" (press F9) in LSMW. The problem is when converting String to Character. Anyone have experience for this?
rgds,
Handoko

Hi
I just tried to create a LSMW in my DEV environment. I didnt get any error when recording. I entered the text in IT41 without any issue. What I am getting in the source code is:
RSTXP-TDLINE(01) Abcde TDLINE_01 ABAP Source Line
Am I missing what you are seeing?
Cheers
Pramod

Pa20(maintain text,display text)

Hi ,
I Need to retrieve the text stored for a emplyee.below i am giving the full details,
In Pa20 transaction if we give the perso. no and select the 0008 infotype.then click on overview tab.then in overview screen if i select any record i.e any period of dates and clicks on display.in display window menu bar
EDIT-> maintain text .
they are maintaing some text in that.if i click on display text the text was displaying.
i need to fetch that data in my custom report.
can anybody helps from where this text can be selected.which ifotype?.
hope my question is understood .
Thanks,
JK.

the following works perfect for me..
*& Report ZP_PA_0008_READ_NOTES *
report zp_pa_0008_read_notes.
infotypes:
0008.
* workfields & internal tables
data w_subrc type sysubrc.
data: key like pskey.
data: begin of ptext occurs 200.
data: line(78).
data: end of ptext.
selection-screen begin of block abc with frame title text-001.
parameters:
 p_pernr like pernr-pernr,
 p_date like sy-datum.
selection-screen end of block abc.
call function 'HR_READ_INFOTYPE'
exporting
 tclas = 'A'
 pernr = p_pernr
 infty = '0008'
 begda = p_date
 endda = p_date
importing
 subrc = w_subrc
tables
 infty_tab = p0008
exceptions
 infty_not_found = 1
 others = 2.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
loop at p0008 where itxex eq 'X'.
refresh ptext.
move-corresponding p0008 to key.
import ptext from database pcl1(tx) id key.
loop at ptext.
 write :/ p_pernr,ptext-line.
endloop.
endloop.
~Suresh

Problem in PA30 Maintain Text

Hi All,
We have recently encountered a problem with maintaining text via PA30. I have searched for solutions for this and the answer i got is to remove the concern infotype from the grouping table V_T582G. This eventually worked. Problem solved, we can now maintain text for concern infortypes.
However, when maintaining infotypes via ESS, there seems to be a problem. Pointing that the infotype is not maintained in V_T582G.
Can anyone please advice us on how to go about this problem? Any suggestion would be greatly appreaciated.
Regards,
Ranilo

Hi Ranilo,
If you maintain ths infotype via ESS then you will need an entry in T582G as ESS use the new infotype framework.
In the past there was a technical restriction which prevents to maintaint text for shared infotypes (ITs with an entry in T582G).
This restrictions has been removed recently via note 1468564 T582A: Cannot activate text maintenance for infotype.
Implement this note, it will allow you to have the text maintenance allowed on shared infotypes.
Hope this help
Sarah

Maintain texts for Infotype 0019 via ABAP.

Hi,
The issue is related to maintaining texts for Infotype 0019. I have a program below. The main problem is I am facing is for some records it inserts text in Infotype (0019) but for some it does not. Can anyone suggest why so or a way to resolve this problem ???
REPORT ytbctest009.
TABLES: pernr, pcl1.
INFOTYPES: 0019.
DATA: key LIKE pskey.
DATA: BEGIN OF ptext OCCURS 200.
DATA: line(72).
DATA: END OF ptext.
SELECTION-SCREEN BEGIN OF BLOCK abc WITH FRAME TITLE text-001.
PARAMETERS: p_pernr LIKE pernr-pernr.
SELECTION-SCREEN END OF BLOCK abc.
ptext-line = 'TEST 1'.
APPEND ptext.
ptext-line = 'Test 2'.
APPEND ptext.
ptext-line = 'Test 3'.
APPEND ptext.
rp-read-infotype p_pernr 0019 0019 '18000101' '99991231'.
SORT p0019 DESCENDING.
READ TABLE p0019 INDEX 1.
p0019-itxex = 'X'.
MOVE-CORRESPONDING p0019 TO key .
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
 infty = '0019'
 number = p_pernr
 validityend = p0019-endda
 validitybegin = p0019-begda
 record = p0019
 operation = 'MOD'.
EXPORT ptext TO DATABASE pcl1(tx) ID key.
Thanks in advance.

Hi Rajashree,
I hope , below code will solve the problem.
Main Code
FUNCTION zhr_mustus_update_it0019.
*"*"Local interface:
*" IMPORTING
*" VALUE(IM_PERNR) TYPE P0019-PERNR OPTIONAL
*" VALUE(IM_USRID) TYPE PA0105-USRID OPTIONAL
*" VALUE(IM_SUBTY) TYPE P0019-SUBTY
*" VALUE(IM_TERMN) TYPE P0019-TERMN OPTIONAL
*" VALUE(IM_MNDAT) TYPE P0019-MNDAT OPTIONAL
*" VALUE(IM_BVMRK) TYPE P0019-BVMRK OPTIONAL
*" VALUE(IM_TEXT) TYPE CHAR30 OPTIONAL
*" EXPORTING
*" VALUE(EX_RETURN_MESSAGE) TYPE STRING
*" VALUE(EX_MESSAGE_ID) TYPE ARBGB
*" VALUE(EX_MESSAGE_NUMBER) TYPE MSGNR
*" EXCEPTIONS
*" SYSTEM_FAILURE
*" COMMUNICATION_FAILURE
REFRESH bdcdata.
REFRESH it_bdc_message.
* Validations
PERFORM validations USING im_usrid im_subty im_mndat
 CHANGING im_pernr
 g_task_date
 g_rem_date.
* Return message
MOVE:
 g_message TO ex_return_message,
 'ZMSGHR' TO ex_message_id,
 g_msgno TO ex_message_number.
* If there any error don't process
CHECK ex_return_message IS INITIAL.
* If reminder date is missing then its creation
IF im_mndat IS INITIAL.
* Fill BDC for PA30 Creation
 PERFORM fill_bdc_for_creation USING im_pernr
 im_subty
 im_text
 g_task_date
 g_rem_date.
ELSE.
* Its a change, Fill BDC for PA30 change
 PERFORM fill_bdc_for_change USING im_pernr
 im_subty
 im_termn
 im_bvmrk
 im_text.
ENDIF.
* Call transaction PA30
PERFORM bdc_call_transaction.
* Return message
MOVE:
 g_message TO ex_return_message,
 g_msgid TO ex_message_id,
 g_msgno TO ex_message_number.
ENDFUNCTION.
All Above Subroutines,
*& Form Validations
* Validations for MUS/TUS
* -->U_USRID User id for TUS
* -->U_SUBTY Subtype 10 - MUS, 11 - TUS
* -->U_MNDAT Reminder date
* <--PERNR Person for MUS
* <--U_TASK_DATE Task date
* <--U_REM_DATE Reminder date
FORM validations USING u_usrid LIKE pa0105-usrid
 u_subty LIKE p0019-subty
 u_mndat LIKE p0019-mndat
 CHANGING u_pernr LIKE p0019-pernr
 u_task_date LIKE sy-datum
 u_rem_date LIKE sy-datum.
DATA:
 BEGIN OF it_tmp_0019 OCCURS 0,
 termn LIKE pa0019-termn,
 END OF it_tmp_0019.
CLEAR g_message.
* Validations for MUS
IF u_subty EQ c_subty_10.
 MOVE sy-datum TO u_task_date.
 IF u_pernr IS INITIAL.
* Person number is missing
 MOVE:
 text-001 TO g_message,
 '003' TO g_msgno.
 ELSEIF u_mndat IS INITIAL.
* Its creation, check if there is already a open item
 SELECT pernr
 FROM pa0019
 INTO u_pernr
 WHERE pernr EQ u_pernr
 AND subty EQ u_subty
 AND bvmrk NE '2'.
 EXIT.
 ENDSELECT.
 IF sy-subrc EQ 0.
* Throw an error if there is already a open item
 MOVE:
 text-006 TO g_message,
 '004' TO g_msgno.
 ENDIF.
 ENDIF.
ENDIF.
* Validations for TUS
IF u_subty EQ c_subty_11.
 IF u_usrid IS INITIAL
 AND u_pernr IS INITIAL.
* User/Person number is missing
 MOVE:
 text-002 TO g_message,
 '005' TO g_msgno.
 ELSEIF NOT u_usrid IS INITIAL.
 SELECT pernr
 FROM pa0105
 INTO u_pernr
 WHERE usrid EQ u_usrid.
 ENDSELECT.
 IF u_pernr IS INITIAL.
* Person number is missing
 MOVE:
 text-001 TO g_message,
 '006' TO g_msgno.
 ENDIF.
 ENDIF.
 IF g_message IS INITIAL.
 SELECT termn
 FROM pa0019
 INTO TABLE it_tmp_0019
 WHERE pernr EQ u_pernr
 AND subty EQ u_subty
 AND bvmrk NE '2'.
 READ TABLE it_tmp_0019 WITH KEY termn = sy-datum.
* There is no open task for today
 IF sy-subrc NE 0.
 MOVE sy-datum TO u_task_date.
 ELSE.
* There is a open task for today, new task should be created next
* available date and reminder date is yesterday's date
 SORT it_tmp_0019 DESCENDING.
 READ TABLE it_tmp_0019 INDEX 1.
 u_task_date = it_tmp_0019-termn + 1.
 u_rem_date = sy-datum - 1.
 ENDIF.
 ENDIF.
ENDIF.
ENDFORM. "VALIDATIONS
*& Form Fill_bdc_for_creation
* BDC data for creation , Transaction PA30
* -->U_PERNR Person
* -->U_SUBTY Subty MUS - 10, TUS - 11
* -->U_TEXT Text
* -->U_TASK_DATE Task date
* -->U_REM_DATE Task date
FORM fill_bdc_for_creation USING u_pernr LIKE p0019-pernr
 u_subty LIKE p0019-subty
 u_text TYPE char30
 u_task_date LIKE sy-datum
 u_rem_date LIKE sy-datum.
* Scree1
DATA:
 l_task_date(10),
 l_rem_date(10).
* Use system date as Task date
WRITE:
 u_task_date TO l_task_date,
 u_rem_date TO l_rem_date.
PERFORM bdc_dynpro USING 'SAPMP50A' '1000'.
PERFORM bdc_field USING 'RP50G-PERNR'
 u_pernr.
PERFORM bdc_field USING 'RP50G-CHOIC'
 '0019'.
PERFORM bdc_field USING 'RP50G-SUBTY'
 u_subty.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=INS'.
* Screen2
PERFORM bdc_dynpro USING 'MP001900' '2000'.
PERFORM bdc_field USING 'P0019-TMART'
 u_subty.
PERFORM bdc_field USING 'P0019-TERMN'
 l_task_date.
IF NOT u_rem_date IS INITIAL.
 PERFORM bdc_field USING 'P0019-MNDAT'
 l_rem_date.
ENDIF.
PERFORM bdc_field USING 'RP50M-TEXT1'
 u_text.
PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
PERFORM bdc_dynpro USING 'MP001900' '2000'.
PERFORM bdc_field USING 'P0019-TMART'
 u_subty.
PERFORM bdc_field USING 'P0019-TERMN'
 l_task_date.
IF NOT u_rem_date IS INITIAL.
 PERFORM bdc_field USING 'P0019-MNDAT'
 l_rem_date.
ENDIF.
PERFORM bdc_field USING 'RP50M-TEXT1'
 u_text.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=UPD'.
ENDFORM. "fill_bdc_for_creation
*& Form fill_bdc_for_change
* BDC data for change , Transaction PA30
* -->U_PERNR Person
* -->U_SUBTY subtype MUS - 10 , TUS - 11
* -->U_MNDAT Reminder date
* -->U_BVMRK Status
* -->U_TEXT Text
FORM fill_bdc_for_change USING u_pernr LIKE p0019-pernr
 u_subty LIKE p0019-subty
 u_termn LIKE p0019-termn
 u_bvmrk LIKE p0019-bvmrk
 u_text TYPE char30.
* Scree1
DATA l_termn_date(10).
WRITE u_termn TO l_termn_date.
PERFORM bdc_dynpro USING 'SAPMP50A' '1000'.
PERFORM bdc_field USING 'RP50G-PERNR'
 u_pernr.
PERFORM bdc_field USING 'RP50G-CHOIC'
 '0019'.
PERFORM bdc_field USING 'RP50G-SUBTY'
 u_subty.
PERFORM bdc_field USING 'RP50G-BEGDA'
 l_termn_date.
PERFORM bdc_field USING 'RP50G-ENDDA'
 l_termn_date.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=MOD'.
* Screen2
PERFORM bdc_dynpro USING 'MP001900' '2000'.
PERFORM bdc_field USING 'P0019-TMART'
 u_subty.
PERFORM bdc_field USING 'P0019-TERMN'
 l_termn_date.
PERFORM bdc_field USING 'RP50M-TEXT1'
 u_text.
PERFORM bdc_field USING 'P0019-BVMRK'
 u_bvmrk.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=UPD'.
ENDFORM. "fill_bdc_for_change
FORM bdc_call_transaction.
DATA:
 l_mode(1) TYPE c VALUE 'N',
 l_lines TYPE i,
 l_msgvar1 LIKE balm-msgv1,
 l_msgvar2 LIKE balm-msgv2,
 l_msgvar3 LIKE balm-msgv3,
 l_msgvar4 LIKE balm-msgv4.
CALL TRANSACTION 'PA30' USING bdcdata MODE l_mode
 MESSAGES INTO it_bdc_message.
* Get last message
DESCRIBE TABLE it_bdc_message LINES l_lines.
READ TABLE it_bdc_message INDEX l_lines.
MOVE:
 it_bdc_message-msgid TO g_msgid,
 it_bdc_message-msgnr TO g_msgno,
 it_bdc_message-msgv1 TO l_msgvar1,
 it_bdc_message-msgv2 TO l_msgvar2,
 it_bdc_message-msgv3 TO l_msgvar3,
 it_bdc_message-msgv4 TO l_msgvar4.
* Prepare message
CALL FUNCTION 'MESSAGE_PREPARE'
 EXPORTING
 language = sy-langu
 msg_id = g_msgid
 msg_no = g_msgno
 msg_var1 = l_msgvar1
 msg_var2 = l_msgvar2
 msg_var3 = l_msgvar3
 msg_var4 = l_msgvar4
 IMPORTING
 msg_text = g_message
 EXCEPTIONS
 function_not_completed = 1
 message_not_found = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 MOVE text-005 TO g_message.
ENDIF.
ENDFORM. "BDC_FIELD
* Start new screen *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM. "BDC_DYNPRO
* Insert field *
FORM bdc_field USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM. "BDC_FIELD
Cheers.
Santosh.

Maintain Text

Similar Messages

Maybe you are looking for