Adding message types to ME21N,Me22N ?

Hi all,
I am creating SO from PO using ALE-IDoc . though i am successfully creating the SO . i have one problem.
i am creating the SO through Message type NEU , but also i have to generate the print out of the PO simultaneously. To this i am using message type NEU1 .
Here the problem is , when i am creating the PO in its messages NEU is added by default with transmission medium ALE. But every time i have to add NEU1 manually with transmission medium Print.
Please specify how to add this NEU1 to the message types in ME21N like NEU, so that no need to add this manually?
Thanks,
Aravind.

Hi,
if you want to delete the NEU message type, go to MN05 and give this message type select the appropriate combination and display the record and delete it.
In case if you want NEU1 to come up automatically, then Go to MN04 give NEU1 message type and then select the key combination document type. then give the Document type has NB( which u are using) and then medium as print out, date/time - 3, language - EN and then communication - LOCL. By doing this next time you create a PO NEU1 will appear in the messages icon in your PO.
Thanks & regards,
Kiran

Similar Messages

Change flag deactivaion for PO output message type during change mode

Hello All,
WE are using automatic message output determination functionality for PO output type. This output type has been configured for creation and change mode under Fine tuning.
Two output type are configured, for example ZAAA is output type for ALE and output type ZBBB for archiving.
Here archiving functionality is used to transfer attachment from ERP system to SUS supplier portal as a pdf file. This is done via enhancement and the attachment transfer is working fine.
During creation mode both the output types are determined and successfully processed and as a result attachment is transferred to supplier portal which is absolutely correct. In the attachment all PO line item can be seen which works well.
Now I change the PO and add a new PO line item, system automatically default both the output type for change mode and upon saving both the output type are successfully processed.
Now here is the problem in change mode only the added PO line item is sent as an attachment to the supplier portal. Here the requirement is see all the PO line items including the once which were newly added.
Solution is if we uncheck the change flag for output type ZBBB during change mode then all the PO line item can be seen under the new attachment with new version.
Please let us know how this functionality can be acheived ... is there an user exit available.
We have a work around where we are running a background job every 3 mins and based on the last successfully processed message for output type ZAAA we are attaching first output type ZBBBfor archiving the changes and then ZAAA for sending the changes along with attachment to Supplier portal.However this solution is a temporary one , we need a concrete solution for this.
Please advise.
Thanks,
Yatin

Hello All,
Thanks for the reply,
But we cannot modify the existing print program as this print program is being used in different countries also.
We already know a solution that during change mode if we remove the change flag from output type ZBBB then all the PO line items along with the recent changes can be seen under the attachment under supplier portal.
The question comes now, how do we automate this processu2026 Is there any standard progam or user exit available.
Manually, if you add a message type ZBBB in ME22N tranasction for creation mode then all PO line item with recent changes get transferred but we need to automate this process for create and change PO transaction.
Thanks,
Yatendra

Same message type in different partner profiles in ALE

Hi,
I have a situation where we need to send an IDoc of message type ORDERS to two partners of type 'LS'. Configured partner profiles in WE20 and added message type for both the partners. Also configured the condition records.Now the question is how the system will know for particular vendors a particular partner 'LS' should be chosen? In condition records we don't have option to configure a vendor for a particular logical system.
Please advice.
Regards,
Krishna

For Vendors, why are you using LS, u need to use LI.

Sending Message Type from the same Logical System to 2 different ports

Hi,
I need to transfer the same message type 'DEBMAS' in the same logical system,
to 2 differenet port - directly to XI (as an IDOC) and to function (as a PROXY),
In XI this are 2 different interfaces.
I see in we21 that when adding message type in outbound I can also write message code or message function so I tried adding an additional row of DEBMAS with message code but it did not work.
Thanks,
Naama

Hey,
This question should not be posted here, but in the XI forum,
anyways,you can do it in 2 ways
1) You can send the message to XI, and in XI it should be configured to send to
two different places, which can be done in the Receiver Communication Channel, one would be IDoc Receiver and another would be a SOAP Receiver. ( here you send one message to XI and XI will send it to the PROXY )
2) You can specify the settings in your Partner profile (we21)and while generating the Port (we20).
Regards,
Samson Rodrigues.

Restricting Message type to 1 receiver-ALE

Dear All
We are using ALE scenario where we ALE idocs from Finance box to HCM box. I am using searlization method for message type and generating idocs from change pointers using program RBDSE01.
One of the message type (CREMAS) is being used in more than one distribution model. The issue is when idocs are generated from change pointers, multiple communication idocs are generated as message type is maintained in more than one distribution model. Is it possible to restrict idocs generated fro change pointers to one receiver?
I have defined distribution model and have added message type SERDAT for searlization. Further filter object(searlization group) is added to this message type. program RBDSE01 is run for this searlization group.
Can someone please help?
Thanks
Sanjeev

Hi Sanjeev,
I can only give you hints as I do not recall the whole procedure exactly
In the easy acces menu go to Tools -> ALE -> IDoc
1. IDoc Type Development -> Logical Messages
2. IDoc Type Development -> IDoc Type for Message
3. Relationships -> Define Link Object Type for Message Type
4. Relationships -> Assign Link Object Type to IDoc Field
5. Relationships -> Assign Business Object to Message Type
6. Engineering Change Management -> Define Change-Relevant Fields
7. Engineering Change Management -> Define Function Module for Evaluation
In all these steps copy the customizing of the original message to your zmessage.
Go to transaction sale:
Modelling and Implementing Business Processes -> Master Data Distribution -> Replication of Modified Data
8. Activate Change Pointers for Message Types (here you need to add your z message)
9. Switch Change Pointer Storage
After that you should be able to run your first test.
Please let me know whether it worked or whether I missed something.
Best of Luck
Andreas

Message Type SYNCH

Hi Experts,
Could you please tell me the purpose of adding message type SYNCH in Partner Profile(WE20) ?
Regards,
Sonal

Hi Sonal,
That's the dummy message type added for determining the RFC destination.
~ Bineah.

BADI for Disabling NetPrice field in ME21N & ME22N based of Material Type.

Hi.
I had a requirement to disable "net price" field while creating or changing a PO (ME21N & ME22N) based on the type of material entered.
Please asssit me in finding the BADI or exit name which can meet my requirement. Thanks.

Hi Ranga nadh,
The BAdi what you have mentioned is correct.
ME_PROCESS_PO_CUST - In this BAdi, we are having a method PROCESS_ITEM. These method is used to process all the Item data. As the field Netprice is at the level. You can use this method.
Here inside this method we are having a parameter IM_ITEM
So, You create a implementation and inside this method you can code here to appear the field in disable mode.
Cheers,
Swamy Kunche

In po my doc type,other users can't do me21n&me22n but they see in me23n

i have created my own document type in po, that document use for me only not other users but other users can see(me23n) display mode but can't do me21n & me22n with my own document type, this option is there in sapmm plez explain
thank u

HI,
For achieving this you have to restrict the authorization for other users in authorization object M_BEST_BSA.
Regards,
Bharat.

Warining Message in ME21N/ME22N in SAP4.6B

Hi all,
I have given a warning message in a user exit(EXIT_SAPMM06E_013). This user exit is triggered on PO SAVE. In ME21, ME22 the warning message is being diaplyed as expected. But in ME21N, ME22N the warning message is not being displayed but is just being ignored. Could you please give the reason for this behavior and the solution to provide the warning message in ME21N, ME22N in SAP 4.6B.
Thanks in advance.
Amit

Hello,
Try using the component MEREQ001 in a project on CMOD.
You have some exits there:
EXIT_SAPLMEREQ_001
EXIT_SAPLMEREQ_002
EXIT_SAPLMEREQ_003
EXIT_SAPLMEREQ_004
EXIT_SAPLMEREQ_005
EXIT_SAPLMEREQ_006
EXIT_SAPLMEREQ_007
EXIT_SAPLMEREQ_008
EXIT_SAPLMEREQ_009
EXIT_SAPLMEREQ_010
Try and see if any of them will work for your case
Hope that will help.
Mário Semedo

ME21N / ME22N sometimes message VE108

Hi,
after upgrade ECC6, SOMETIMES, when i create or modify purchase order (ME21N, ME22N) the custom price condition (Z015 - discount price) doesn't determined.
In pricing analysis there is an error message VE 108.
After manually updating prices, doesn't work too.
Record condition for all materials are correct.
WHY??
Thanks a lot!

Please check the solution on the below:
[Condition record exists, but has not been set;
[Condition record exists, but has not been set in sd pricing;

GR Message in ME21N/ME22N (SAPLMEGUI)

Hi,
In T-code ME21N/ME22N, under the item overview section, when a user selects an Account Assigment Category, I need to check the "GR message" box under Header section.
I found a couple of user exit, but all these exit do not allow us to change the SAP standard field. This is also documented in the SAP documentation. If I go in debug and change the field MEPO1226-WEAKT it will work, but these fields are not accessible from the user exits.
I also looked at using field exit, but that won't wont. I also looked at the config (OME9) and was not able to find anything in there also.
Does anyone have any suggestions?
Thanks for you help.

Hello,
Try using the component MEREQ001 in a project on CMOD.
You have some exits there:
EXIT_SAPLMEREQ_001
EXIT_SAPLMEREQ_002
EXIT_SAPLMEREQ_003
EXIT_SAPLMEREQ_004
EXIT_SAPLMEREQ_005
EXIT_SAPLMEREQ_006
EXIT_SAPLMEREQ_007
EXIT_SAPLMEREQ_008
EXIT_SAPLMEREQ_009
EXIT_SAPLMEREQ_010
Try and see if any of them will work for your case
Hope that will help.
Mário Semedo

Send mail with Z Message Class in me21n and me22n

Hi everyone, i'm new at the forum and this is may first post so i ask for apologies if i post it in the wrong please.
Well my question is this, i have an z class message in the NACE transaction that it's suppose to send a mail, well if i use the standard program SAPFM06P form ENTRY_NEU with a sapscript it send correctly the mail and i can display it in the SOST transaction, but i need it to display a smartform not a sapscript, so i copy the program to Z and make it call my smartform, if i go now to the me21n/me22n/me23n an make a print preview it's display my smartform correctly, to this point it's all ok, but the problem is that when i modify something in the order and save, my Z message class does not send the mail (i can't see it in the SOST transaction)
I was looking and it seems the problem is that the SOST and the SOOD table are not update but the NAST table does, so when i go to the SOST transaction it doesn't find the data to display.
I know that the update it's done in the form BUCHEN of the SAPLMEPO, but i can't find where.
Does anybody know how can i fix this problem? basically i want the me21n and me22n send the mail.
Thanks a lot

Thanks for your quick answer, I'll check and let you know any news
PD: what do you mean by "you need to maintain condition records as external send. then only it will send the mail automatically"?
Edited by: -tk85- on Jan 18, 2012 3:32 PM

Adding a new message type to Report RHALEINI to send HR Master Data

I have extended Basic IDoc type HRMD_A07 with custom segments, and I want to send this vis report RHALEINI. PRoblem is I cannot see it in the Receiving System Message Type frop down list. IS it so that I must set up a Master Data Distribution Model with that message type before the report will show it in the list?
BR,
Tony.

Hi Tony,
I have the same question. Did you find a solution for this?
Thank you
Best regards
Christian

ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

Dear All Expert,
I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
Please find the below ABAP Runtime Error.
Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
Date and Time          10.02.2011 11:13:07
Short text
     Change of a Dictionary structure at runtime of a program.
What happened?
     Runtime error
     The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
      terminated because one
     of the statements could not be executed at runtime.
What can you do?
     Restart the program.
     If the error persists, contact your SAP administrator.
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
      changed
     during the flow of the transaction.
     As the type was already used in the old version
     and in the new type should be used in the same transaction in the new
      version, the transaction had to be cancelled to avoid inconsistencies.
How to correct the error
    Try to restart the program.
System environment
    SAP-Release 700
    Application server... "iqe"
    Network address...... "172.25.0.85"
    Operating system..... "Linux"
    Release.............. "2.6.9-55.ELsmp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "iqe"
    Database type..... "ORACLE"
    Database name..... "IQE"
    Database user ID.. "SAPSR3"
    Terminal................. "MUMJML5727"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 26 2010 20:17:07"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 285
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 16192
EM...... 25139088
Heap.... 0
Page.... 40960
MM Used. 8038136
MM Free. 4528408
User and Transaction
Client.............. 600
User................ "JKMM"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
Screen.............. " "
Screen line......... " "
Information on where terminated
    The termination occurred during generation of the ABAP/4 program
     "CL_IM_WRF_MM_PROC_PO==========CP".
    The termination occurred in line 213
    of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
     calling the editor 2130).
Source Code Extract
Line SourceCde
183   DATA: l_flag TYPE wrf_pbas_boolean.
184
185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
186     IMPORTING
187       e_preview_flag = l_flag.
188
189   IF NOT l_flag IS INITIAL.
190
191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
192
193     MOVE im_header ?TO l_header.
194
195     CALL METHOD l_header->if_output_mm~preview( ).
196
197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
198
199 ***$ Widening Cast for printing information.
200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
201 **      EXPORTING
202 **        im_header = l_header.
203
204 * Printing Preview
205 * IF NOT gv_preview IS INITIAL.
206 *    CALL METHOD l_header->if_output_mm~overview( ).
207 *    CALL METHOD l_header->if_output_mm~preview( ).
208 * clear gv_preview.
209   ENDIF.
210
211 * ENDIF.
212
>>>>> ENDMETHOD.
Internal notes
    The termination was triggered in function "ab_RxDdicStruShareFailed"
    of the SAP kernel, in line 2539 of the module
     "//bas/700_REL/src/krn/runt/abtypload.c#11".
    The internal operation just processed is " ".
    Internal mode was started at 20110210111306.
    Name of the changed type......: "WRF_POHF_KOMP_STY"
    New version of the type.......: 20070508193207
    Old version of the type.......: 20070508193207
    New user......................: "Type" "WRF_POHF_KOMP_STY"
    Version of the new user.......: 20070508193207
    Old user......................: "???" "???"
    Version of the old user.......: "???"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(CTrcStack2+0x78)[0x6cbb78]
(CTrcStack+0xb)[0x6cc17b]
(ab_rabax+0x3be5)[0xb8d985]
(_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
(_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
(_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
(_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
(ab_GetView+0xc1d)[0xb0ee1d]
(_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
(_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
(_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
(_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
(sc_blkle+0xdd)[0xec6e4d]
(rs_oper_abap1729+0x37)[0x10eb237]
(rs_expan_abap+0xa1996)[0xfd7a2a]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_inclu+0x5fa)[0xe0d50a]
(rs_oper_abap2160+0x3a)[0x1115d6a]
(rs_expan_abap+0xcd41d)[0x10034b1]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_checkStart+0x41)[0xe1ac51]
(cg_generate+0xb65)[0xe57755]
(ab_gabap+0x14a)[0xb01a5a]
(dy_gen_abap+0x63c)[0x74428c]
(ab_genprog+0x13d3)[0xb03d13]
(_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
(_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
(_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
(_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
(_Z11ab_FillCfixtj+0x65)[0x957ae5]
(_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
(_Z8ab_jaboov+0x623)[0x959793]
(_Z8ab_extriv+0x607)[0x8ba9c7]
(_Z9ab_xeventPKt+0x1c1)[0xa1c021]
(_Z8ab_triggv+0x9c)[0xa1c77c]
(ab_run+0x97)[0xbde5c7]
(N_ab_run+0x9)[0x736359]
(dynpmcal+0x669)[0x7333b9]
(dynppai0+0x8eb)[0x734d9b]
(dynprctl+0x3e9)[0x733db9]
(dynpen00+0x4a5)[0x726eb5]
(Thdynpen00+0x359)[0x541bd9]
(TskhLoop+0xc49)[0x54d999]
(ThStart+0x20f)[0x55b29f]
(DpMain+0x2da)[0x4bd49a]
(nlsui_main+0x9)[0x4910c9]
(main+0x33)[0x491103]
/lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
Please help me to resolve the issue.
Thanks & Regards
SKK

read this part again: The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
how often had you restarted ME21N before you posted this message?
In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

Dump While Executing ME21N, ME22N and ME23N

Hi,
Am getting the below Short Dump while executing ME21N, ME22N and ME23N.
Runtime Errors         SYNTAX_ERROR
Date and Time          08.07.2009 15:41:00
|Short text
Syntax error in program "ME_PROCESS_PO_CUST============CP ".
|What happened?
|    Error in the ABAP Application Program
|
|    The current ABAP program "CL_EX_ME_PROCESS_PO_CUST======CP" had to be
|     terminated because it has
|    come across a statement that unfortunately cannot be executed.
|
|    The following syntax error occurred in program
|     "ME_PROCESS_PO_CUST============CP " in include
|     "ME_PROCESS_PO_CUST============CM000 " in
|    line 14:
|    "The specified type cannot be converted into the target variables."
|    " "
|    " "
|    " "
|
|    The include has been created and last changed by:
|    Created by: "SILABAP "
|    Last changed by: "SILABAP "
|    Error in the ABAP Application Program
|
|    The current ABAP program "CL_EX_ME_PROCESS_PO_CUST======CP" had to be
|     terminated because it has
|    come across a statement that unfortunately cannot be executed.
|Error analysis
|    The following syntax error was found in the program
|     ME_PROCESS_PO_CUST============CP :
|    "The specified type cannot be converted into the target variables."
|    " "
|    " "
|    " "
|Trigger Location of Runtime Error
|    Program                                 CL_EX_ME_PROCESS_PO_CUST======CP
|    Include                                 CL_EX_ME_PROCESS_PO_CUST======CM001
|    Row                                     1
|    Module type                             (METHOD)
Module Name                             IF_EX_ME_PROCESS_PO_CUST~INITIALIZE
|Source Code Extract
|Line |SourceCde
|>>>>>|method IF_EX_ME_PROCESS_PO_CUST~INITIALIZE.
|    2| CLASS CL_EXIT_MASTER DEFINITION LOAD.
3
|    4| DATA l_badi TYPE REF TO ME_PROCESS_PO_CUST.
5
6
7
8
9
|   10| TRY.
11
|   12|    GET BADI l_badi
|   13|     CONTEXT me.
14
|   15|    CALL BADI l_badi->INITIALIZE
|   16|.
17
18
19
|   20|    CATCH CX_BADI_NOT_IMPLEMENTED CX_BADI_INITIAL_REFERENCE.
Please let me know is there any OSS note to resolve the Issue.
Thanks,
Subas

Hi,
when I try to do the same in my system SAP gives me an information message as follows:-
Changes to transported Business Add-In definitions are incompatible
Message no. ENHANCEMENT236
Diagnosis
This business add-in definition has already been transported. Subsequent changes could invalidate existing business add-in implementations.
System Response
The runtime behaviour is no longer predictable. Syntax errors or short dumps may occur.
Procedure
If possible, do not make these changes. Alternatively, create a new business add-in definition incorporating the changes and use it, along with the existing definition.
It clearly indicates that the BADI definition should not be changed if active implementations already exists.
I am really now not sure how to solve your issue.
Try deactiviting the standard BADI implementation.
Then again add the filter and then remove it.
And then try activating the BADI implementation once again.
Regards,
Ankur Parab

Adding message types to ME21N,Me22N ?

Similar Messages

Maybe you are looking for