ME21N-Clear error at header level

Hello Experts,
I have a requirement to throw an error message in ME21N if the PR's Sale order has credit limit exceeded.
I have done this with exits. Once the error message is thrown, this error message sits at the header level. Even when deleting the erroraneous line item, this message is not cleared.
I want to remove this message at header level when this erroraneous record is deleted. Please guide me for this.
Thanks
Seema

Hi,
Deactivate that Exit and do this with the BADI.
BADI for this is ME_PROCESS_PO_CUST.
There is one method Process_header. Do the validation in this method for the header level.
Hope this will be easy comparing with Exits.
With Regards,
Sumodh.P

Similar Messages

TO ADD TAB AT HEADER LEVEL IN ME21N

Hi guys
I have to add a tab at header level of ME21N using BADI ME_GUI_PO_CUST and ME_PROCESS_PO_CUST
can someone guide me how to do this?
Thanks

Hi,
Try with SMOD enhancement MM06E005. I know this works well for adding a tab in PO header or item level . Read OSS 407975 for implementing this screen exit
here i am pasting OSS Notes and if you need clearly then login into service.sap.com
Symptom
You are using SAP customer enhancement MM06E005. There is no sample source code for this enhancement.
Other terms
User exit, customer enhancement, MM06E005, example, sample
Reason and Prerequisites
You want to activate user exit MM06E005. Note that this is a consulting note and not a correction of the user exit.
Solution
You can use the sample source code attached here to recognize the basic functions of the exit. This example is, however, only one of many options that are offered by the customer enhancement.
The sample source code includes the following functions:
Supply of an additional field on header level
Supply of an additional field on item level
Derivation of a field on item level from the copied reference document
Now, in order to be able to use the sample source code, you must create field ZZFLAG on the header level of the document and field ZZFIELD on the item level.
Double-click on Include table CI_EKKODB
Enter the following values:
Name    Component type DType Length DecPlace Short text
ZZFLAG CHAR1          CHAR 1      0        1-digit indicator
Save and activate the include table.
Double-click on Include table CI_EKPODB
Enter the following values:
Name    Component type DType Length DecPlace Short Text
ZZFIELD CHAR1          CHAR 1      0        1-digit indicator
Save and activate the include table.
In order to activate the sample source code, you additionally have to carry out the following changes on screens 0101 and 0111.
1. Screen 0101: Create the following fields:
              "Checkbox"            Name: EKKO_CI-ZZFLAG
2. Screen 0111: Create the following fields:
              "Input/output field" Name: EKPO_CI-ZZFIELD
              "Pushbutton"          Name: BUTTON
                                    FctCode: ZZDETERMINE
The following assignments apply to the sample source code:
EXIT_SAPMM06E_006 --> LXM06F36
EXIT_SAPMM06E_007 --> LXM06F38
EXIT_SAPMM06E_008 --> LXM06F37
EXIT_SAPMM06E_009 --> LXM06F39
EXIT_SAPMM06E_016 --> LXM06F41
EXIT_SAPMM06E_017 --> LXM06F42
EXIT_SAPMM06E_018 --> LXM06F40
Copy the source code from the attachment and insert it into the corresponding function modules. Save and activate the function modules.
Create the following variables in the corresponding TOP include in order not to get any syntax errors:
INCLUDE ZXM06TOP
data: gl_aktyp type c,
      gl_no_screen type c,
      gl_rekko like ekko,
      gl_ekko_ci like ekko_ci,
      gl_ekpo_ci like ekpo_ci,
      gl_ekpo like ekpo,
      gl_ucomm like sy-ucomm.
types: begin of ekpo_tab,
          ebeln like ekpo-ebeln,
          ebelp like ekpo-ebelp,
          ekpo like ekpo,
       end of ekpo_tab.
data: gt_ref_ekpo_tab type table of ekpo_tab.
Save and activate the TOP include.
On header level, you can now store a character, X or space, via field ZZFLAG on the database with the document and read it also again.
On item level, you can fill field ZZFIELD with a one-digit value and save it with the document. If you copy this document, the system displays an additional function button on tab page "Customer data". If you press this button, the value of the reference document is copied to field ZZFIELD.
If you want to store the source code as sample source code in your system, start Transaction SMOD. Enter MM06E005 as an enhancement. Select "Components". Press "Change". Position the cursor on the corresponding module and choose "Sample code". Create the corresponding include and copy the source code from the note. Save the include. Note that, of course, syntax errors may occur when you check components. This is because the includes of the sample code are not integrated into a program but rather are completely independent and, therefore, do not have any relationship to each other either. For this reason, only save the include and do not activate or check it. The sample code has to be copied into the corresponding function modules in order to become active.
If you use the user exit in the new purchase order, it is not guaranteed that the customer screen is always processed. To make sure that possible required fields are checked, include a corresponding message into the EXIT_SAPMM06E_012. This screen is always processed.
Header Data
Release Status: Released for Customer
Released on: 07.09.2006 13:07:34
Priority: Recommendations/additional info
Category: Consulting
Primary Component: MM-PUR-PO Purchase Orders
Secondary Components: MM-PUR-GF-CE Customer Enhancements
I have not done BADI for PO,so i am not sure that whether BADI will work for Screen exit or not
Thanks
Seshu

Additional tab at header level in ME21N through BADI ME_GUI_PO_CUST

Hi,
I want to have additional tab at header level in ME21n through BADI ME_GUI_PO_CUST. But after all effort I am not getting display of tab. Let me explain what i did till now
1. Appended table EKKO with field
2. Create one function Group -under that
A. Created one Include u2013Paste the code given
DATA: call_subscreen   TYPE sy-dynnr,
      call_prog        TYPE sy-repid,
      call_view        TYPE REF TO cl_screen_view_mm,
      call_view_stack TYPE REF TO cl_screen_view_mm OCCURS 0,
      global_framework TYPE REF TO cl_framework_mm,
      global_help_view TYPE REF TO cl_screen_view_mm,
      global_help_prog TYPE sy-repid.
FORM SET_SUBSCREEN_AND_PROG *
--> DYNNR *
--> PROG *
--> VIEW *
--> TO *
--> CL_SCREEN_VIEW_MM *
FORM set_subscreen_and_prog USING dynnr TYPE sy-dynnr
prog TYPE sy-repid
view TYPE REF TO cl_screen_view_mm.
call_subscreen = dynnr.
call_prog = prog.
call_view = view.
ENDFORM. "set_subscreen_and_prog
B. Created one screen (9000)
3. Implemented BADI ME_GUI_PO_CUST and paste the code.
data: ls_subscribe like line of re_subscribers.
CHECK im_application = 'PO'.
CHECK im_element = 'HEADER'.
CLEAR re_subscribers[].
ls_subscribe-name = ' ZMMSCR1'.
ls_subscribe-dynpro = '9000'.
ls_subscribe-program = ' ZMMSCR1'.
ls_subscribe-struct_name = 'EKKO'.
ls_subscribe-label = text-001..
ls_subscribe-position = 15.
ls_subscribe-height = 7.
append ls_subscribe to re_subscribers.
Please help me what s going wrong .and what else I will do to get success.
Edited by: Vishal A Vijaywargia on Jul 29, 2009 2:24 AM

Hi Prosengit,
I am not aure about u r BADI,
BUt last week i have custom tab in the PO header data using this enahncement 'MM06E005'.
IN thi senhancement u have thrre screen exits.In this enhancement
SAPMM06E        0111 CUSTSCR1 SAPLXM06        0111 Subscreen: PO item
u can add subscreen and u can add u r own fields here .
and u can write u r code in 'EXIT_SAPMM06E_006'.
if u want to change the title of the program.
Go to program SAPLXM06 then go to text element give text symbol no as '111' and u can change the title of u r tab.
I hope this solves u r problem.

Issue in adding new tab in PO Header Level on ME21N

Hello,
As there are many thread where it has mention how to implement badi to get the required output.
Similarly, i had used the badi ME_GUI_PO_CUST and the method IF_EX_ME_GUI_PO_CUST~SUBSCRIBE.
My Doubt :
From the below sample code, from where i have to create the subscreen, Program name.
For ME21N the program name in status is showing SAPLMEGUI.
Sample Code from other thread and my doubts are next to it..
CHECK im_application = 'PO'.
CHECK im_element = 'HEADER'.
CLEAR re_subscribers[].
ls_subscribe-name = 'SAPLZPONEWTAB'.   "This is the name of subscreen but it shows the standard one (shall i create a program and then add a subscreen and use here?)
ls_subscribe-dynpro = '9000'.
ls_subscribe-program = 'SAPLZPONEWTAB'. "Shall i use the program name SAPLMEGUI here
ls_subscribe-struct_name = 'ZPONEWTAB'.    "Why this is required, as in my case i want to show some fields from EKKO table
ls_subscribe-label = text-001.
ls_subscribe-position = 15.
ls_subscribe-height = 7.
append ls_subscribe to re_subscribers.
Please advice...

Hi,
Thanks for the reply.
I have done the things..but, i can't see the tab in the header level.
Below is my code with my comment.
Note :
I created a Function Group by name SAPLZPOHEADER.
In se80 by giving the name ZPOHEADER i created a subscreen. Also created a structure as ZPOHEADER using it displayed the fields in the screen.
Code under IF_EX_ME_GUI_PO_CUST~SUBSCRIBE :
DATA: ls_subscriber LIKE LINE OF re_subscribers.
      CLEAR: re_subscribers.
      REFRESH: re_subscribers.
IF im_application = 'PO' AND im_element = 'HEADER'.
    CLEAR re_subscribers[].
   ls_subscriber-name = subscreen1. "As per the sample code i double click and set the attributes of it as same as sample code.
   ls_subscriber-dynpro = '9000'. "This is the screen no
   ls_subscriber-program = 'SAPLZPOHEADER'.   "Name of the FM Group/Program
   ls_subscriber-struct_name = 'ZPOHEADER'.     "Structure Name
   ls_subscriber-label = text-001. "Created label as 'doc header'
   ls_subscriber-position = 11.    "Given the position as i want after 'status' in ME21N
ls_subscriber-height = 7.
APPEND ls_subscriber TO re_subscribers.
Is anything remaining as in debug mode it fills the re_subscribers and go the 'Create Object' but, can see it in display.
Pls help...

How do i pass the error message at header level in CRMD_order

Hi all,
i got one requirement like when i create/change the sevice order (CRMD_ORDER)
if net_value is more than 1000 i have to set the message 'E' like 'order is blocked'
else 'approved' at header level before going to save the order.
please help me out it is high priority and as i am new to CRM.
thanks in advance.
Thank you,
Madhu.

Anil
You have to look for a BADI to add the Error Message.
Also use the FM CRM_MESSAGES_DISPLAY to display the message !
Thanks
<b>Allot points if this helps!</b>

Clearing Sales Tax at Header Level in an Order

Hi,
I have a requirement to not charge any tax on an order if the credit card used on the order is a government credit card. Currently I have implemented this logic in USEREXIT_SAVE_DOCUMENT_PREPARE. I am able to clear out the sales tax at the line level but this change does not reflect at the header level. I have to manually click on update pricing to zero out the tax displayed at the header level. I could not find a variable to tap into header level pricing condition and tax value field.
I would greatly appreciate if any one can give me some pointers on where to look for header level data for tax. Also, is there any better user exit to implement this functionality.
Folliwing is the code I am using to clear out line item level tax:
          LOOP AT XKOMV INTO WA_XKOMV WHERE KSCHL EQ 'UTXJ'.    "GET THE TAX CONDITION
              CLEAR WA_XKOMV-KWERT.                               "Set the TAX to 0
              CLEAR WA_XKOMV-KAWRT.
              CLEAR WA_XKOMV-KBETR.
              MODIFY TABLE XKOMV FROM WA_XKOMV
                TRANSPORTING KWERT KAWRT KBETR.
          ENDLOOP.
          LOOP AT XVBAP INTO WA_XVBAP.    "GET THE TAX VALUE
              CLEAR WA_XVBAP-MWSBP.                               "Set the TAX to 0
              MODIFY TABLE XVBAP FROM WA_XVBAP
                TRANSPORTING MWSBP.
          ENDLOOP.
Thanks,
Paresh

Hi,
In the case of sales cycle, All the item level taxes are summirised and come to the header level. So we can't find the conditions at header level for taxes. Check the user exit , because, the values are already moved to the header level structure and then you are clearing the item level taxes. I hope thats why the changes are not reflected in header level.
Regards,

New Tab on header level for me21n/me22n/me23n

Hi Friends
i have created a new tab on the me21n/me22n/me23n header level using the exit
MM06E005 , The tab is displayed but i am not unable to udate the records into the
EKKO Table whereas i have added my field in the include of EKKO CL_EKKODB
Kindly somebody help me with elaborated steps .
Thanks & Regards
Digvijay Rai

Hi Digvijay,
Once the data is entered on the screen ..code is written to update the table ie...
flow of data from custom screen for header is OK..but for display and change we need to
import the data in a similar manner to the customer subscreen or the tab added in header level
As you can see the following 3...code must be done in EXIT_SAPMM06E_006/007 to fetch data to customer subscreen for display/change actions..use 006/007 for PBO/PAI actions..
EXIT_SAPMM06E_006   Export data to customer subscreen for header(PBO)....INCLUDE ZXM06U36
EXIT_SAPMM06E_007   Export data to customer subscreen for header(PAI)....INCLUDE ZXM06U38 .
EXIT_SAPMM06E_008   Import data from customer subscreen for header
Pls check and revert..in addition
go to smod->MM06E005-> "documentation" -> Display to read more on documentation about data flows and exits used for it
Hope it helps
Regards
Byju

Error in confirmation of Transfer orders at Header level (TC LRF2)

Hello All,
A transfer order has single item. It has got confirmed at the item level for the full quantity. The confirmation switchbox at item level is checked in by the system automatically. But in header level the switch box is not checked in.
While trying to confirm the Transfer order at header level, the error message shows that the Transfer order is already confirmed. But the Transfer order still exists in LRF2.
Thanks in Advance.
Regards,
Sasi.

Hi Marcos
Note 566995 is an old correction note, which is probably already implemented on your system but it describes the standard system design regarding confirmations posted in mass processing transactions:
When you enter an operation confirmation via the order info system or the mass processing the system now sets the confirmation type to 'Automatic final confirmation' as well as the indicator 'Post open reservations'. Thus the system automatically generates a final confirmation when you confirm the whole planned quantity and the operation receives status CNF (finally confirmed) instead of PCNF (partially confirmed).
System is designed that way because a mass processing transaction will be generally executed in background mode and a huge number of confirmations can be posted at the same time. Therefore, user will not be able to enter any value to the confirmation.
If you don't want this behaviour you could use the BAPI
BAPI_PRODORDCONF_CREATE_HDR to develop your own mass processing transaction to post confirmations.
BR
Caetano

Error in entering header level conditional value - toomany line items to PO

Hi experts
I have an issue while processing a PO. While entering condition values like Freight, Customs duty etc in header level where the order contains more than 1000 line items, i am getting an error " too many line items, msg no.899". Can somebody, guide on this how this can be resolved.
rgds
Raghu

HI Raghu,
The only possible way is to create two diffrent PO's.
As you have maintain various conditions, this will lead to updation of many FI documents at the time of GRN.
This is SAP Limitation.
Regards,
Amit
njoy SAP..
njou Life....

PO header level error

Gurus,
I have an issue on the header level which says Source system is required field. Please specify.
Can some one tell me what this error is?
Regards
MV

Hi
If it is during creation of PO
check customization
SPRO>MM>Purchasing>Purchase Order>Define Screen Layout
there is
for your case Supplying Plant
and Source Stock Type
should be Opt.entry checked.
If it is Reqd.enty change please
Best Regards

Clear IDOC creation when only header level changes are made ME22N.

Hi All,
when the PO is on changed in the header level only(for example header texts and header code) and when we execute RSNAST00 one BADI getts triggered which checks if the Item category is 9 and badi will clear the IDOC creation.
If the PO item category is = 9, the IDOC must not be created. This badi works fine if the changes are made at
1)at Item level
2)both header level and Item level
In case of 1 and 2 we have both header segment E1EDK01 and item segments E1EDP01.As a result it checks for the item category in the item segment.so idoc is not created.
3)BADI is not working when the changes are made at the header level only. The IDOC is getting created even though the PO has the item category as 9.
I found in this case only header segments are availble while debugging and the item segments are not there to check the condition for the item category.
Please any one can suggest me possible solutions to clear idoc creation when only header level changes are made ME22N.
The BADI used is as below.
DATA : lwa_data TYPE edidd.
DATA : lw_dp01 TYPE e1edp01.
DATA : lwa_control TYPE edidc.
CHECK idoc_control-rcvprn = '3PL' AND idoc_control-idoctp = 'ORDERS05'.
LOOP AT idoc_data INTO lwa_data.
    IF lwa_data-segnam = 'E1EDP01'.
      lw_dp01 = lwa_data-sdata.
      IF lw_dp01-pstyp = '9'.
        CLEAR create_idoc.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDMETHO
Thanks in advance.

Hi all,
Is there any way that I can get the item category details when Only header level changes are made to the PO in ME22N and only header segments are available in the IDOC.
Is this possible:- Fetch the po number and item category details from ekpo table that matches with the header segment po number and then check for item category value to clear the idoc creation?
Any information is helpfull.
Edited by: Selina.selk on Nov 20, 2009 1:39 PM
Edited by: Selina.selk on Nov 20, 2009 2:49 PM

Heading level hierarchy errors when topics are in TOC more than once

I have discovered that the hierarchy in the Heading levels in
the Printed Documentation will differ from than in my online help
table of contents hierarchy, and that the problem is due to topics
that are intentionally in the TOC more than once.
For example, in chapter 5 of a particular help system the
hierarchy should be:
Heading 1 < Chapter 5 title from top-level book>
Heading 2 <title of second level book>
Heading 3 <title of topic that appears under second-level
book>*
What I actually get is:
Heading 1 < Chapter title from top-level book>
Heading 2 <title of second level book>
Heading 4 <title of topic that appears under second-level
book>*
* This same topic appeared in an earlier chapter. In that
chapter it was really at a Heading 4 level.
Due to company styles, etc. we use a numbering system at the
headings and in the TOC, so instead of
5
5.1
5.1.1
I erroneously get
5
5.1
5.1.1.1
This type of hierarchy issue appears multiple times in this
particular document (which I inherited by the way.)
Other than restructuring the document to not reuse topics in
different places in the TOC, is there a solution or a workaround
for this problem?
What I am doing so far, is generating the Print Documentation
one chapter at a time. As long as a topic is not reused with the
same chapter, my hierarchy of heading levels is maintained;
otherwise, it is not. Then I can put the chapters back together
after fixing the few places that still have heading level problems.
This however, will be quite cumbersome as this document is
translated into nine other languages.
I am using RoboHelp X5 for Word / Word 2003 for the source
and most of the translations; RoboHelp Asian Edition, Simplified
Chinese / Word 2003 for the Chinese translation. The heading level
hierarchy error occurs in both versions.

>> AF: I've commented in sections...
Without Maintain Heading Levels, RH will apply heading levels
to the books and then the topic levels will get bumped down. So a
top level book will be Heading 1 and the Headings in the topic will
get bumped down to 2, 3 and 4 etc. If then you have another book
one level down so that it gets Heading 2 applied, the same topic
but under the level two book would then get 3, 4 and 5 applied.
That is not the original problem but hopefully we are agreed
that is how things work on that.
>> Yes - that is the expected behavior. When it didn't
happen as expected, that's what led me to the discovery of the
cause of the problem (topic reuse).
Your problem was that firstly Heading 3 got bumped to Heading
4 if the same topic was inserted into the TOC twice. I assume it
was OK in the first instance, or is it that when you add it twice
it goes wrong everywhere?
>> Your assumption is correct. First occurrence is
correct. Second, third, and fourth (yes - there is one topic that
is used 4 times! ) are not correct based on TOC hierarchy.
On the numbering, nothing surprises me. If you look at my
site you will see that for RH HTML, i gave up on getting it right.
I have had many queries on this and more than a few people have
indicated they will work on the problem and get it working. I'm
still waiting. There are many posts about outline numbering
problems. Has anyone got it working satisfactorily?
>> I don't really have numbering problems. The
numbering is following the RoboHelp-generated hierarchy and the
.dot template that I apply. It's just that the RH-generated
hierarchy and its heading levels don't correspond to the "real"
hierarchy because of the reuse issue.
I have seen various Word gurus maintain that numbering has
not worked entirely satisfactorily since Word 2! Also enough posts
to convince me this is a Word issue, not a RH issue.
If you want to create a new project and knock something up
that demonstrates this problem, by all means zip it up and send it.
I'll assume it will be a small project and zip to less than 5mb. If
more, contact me first.
>> Unless you have RoboHelp X3 Asian Edition,
Simplified Chinese, there is really no need. I plan to either avoid
the reuse issue in the source, or build the print doc in sections
which is easy enough in RoboHelp X5 for the non-Chinese languages.
It is in the older Asian edition where the problems are compounded
by the omitted reuse topics. If you do have RoboHelp X3 Asian
Edition, Simplified Chinese and want to experiment, I can send you
a cut-down version of the project. Don't feel obligated though;
unless you can read Chinese (I can't) it is very tedious to work
with.

Header level pricing condition error

Hi Friends,
In a PO, I have 5 line items. I am giving freight condition type at header level for the entire po as Rs. 500. But the system calculates the freight charge as 500*5=2500. The freight condition type FRB1 is a fixed charge condition type.
The client wants the absolute freight charge should be for the entire PO.
Please advice how to solve this issue.
Thanks & Regards
Satya

Hi,
the scales have nothing to do with this, they just allow different prices to be stored for different quantities.
But have you had a look at the "qty relevant" flag on the condition type?
Please do check the flags that are set, these do control the calculation.
Also make sure that you are using a condition type that has the "header conditions" flag set on. If you choose one that has only the item condition set on this may not be correct.
FRB1 (the one that you said that you are using) is an ITEM condition and should not be added to the header.
Steve B

Require new tab at header level in ME21N using BADI

Hi All,
My requirement is add new tab with 8 new fields plus one button. On pressing this button header data need to copy at item detail level. I found two BADI's for that.
ME_GUI_PO_CUST & ME_PROCESS_PO_CUST. Till now I am able to create new tab with require fields.
Now help to put how to transfer data from header level to item detail level on pressing newly created push button.
Also tell me how these data will save in EKKO table.

Hi Vikas,
hOPE U CAN USE
PROCESS_HEADER
PROCESS_ITEM methods of the badi used and the data will be stored in EKKO table if u populate them .
let me know if any issues ....
regards

Error message at SC Header level

Hello,
I've made changes to check for approval notes to be mandatory when a shopping cart is rejected using the CHECK BAdI. The message doesn't come up when rejecting at header level, only when rejecting at item level is then that it comes up.
Your assistance will be appreciated.
TX
Chris.

Hello,
I think this badi is not very efficient when rejecting from the inbox (header level), allready encounter pb with this.
Anyway, you'll need to go into the detail screen to add an approval note. Why not simply deactivate the direct approve and reject button from the inbox (dynamic columns for integrated inbox) ?
Rgds,
Pierre

ME21N-Clear error at header level

Similar Messages

Maybe you are looking for