ME9F Issue

Hello Expert,
We are into support project. We have an issue in ME9F transaction. For us the delivery address of the PO is storage location address. While displaying the PO print preview system is picking up the correct delivery address that is the storage location address details, however while issuing the output in ME9F for a particular PO, system is taking the plant address as delivery address though in PO print preview it is showing the correct storage location delivery address.
Why system is showing two different delivery address, that is in ME23N PO print preview storage location address details where as in ME9F it is taking plant address as delivery address.
Could anybody tell me what is root cause for this issue and how to rectify it.
Regards
Bala

hi,
Please get the PO output form logic checked from ABAPr. It seems that in form logic is given for Plant address.
Also you need to check the form assignment whether done correctly or not. Normally Delivery address in PO is Plant address, you can check the same in PO delivery add. filed and you out put logic is picking the same value.
More over we can give you the possiability only actual scenario can be explained by ABAPr only after seeing the PO form logic.
regards,
Ranjan

Similar Messages

Issue in me9f transaction po printing.

Hi
     in me9f when try to print a po, there was a z program
     ZPOPRINT which prints it, i think it is a routine.
     it is giving a dump. i want information on routines
     regarding this.
Thanks & Regards,
Abhimanyu.L

Hi,
     the short dump.
Error in ABAP application program.
    The current ABAP program "ZPOPRINT" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_CONVERSION_OVERFLOW',
     was neither
    caught nor passed along using a RAISING clause, in the procedure "PRINT_SRVPOS"
     "(FORM)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    A value generated during processing is too large for the
    field "ML_ESLL-NETWR" of the program "ZPOPRINT".
189 *   ml_esll-brtwr = ml_esll-brtwr / ml_esll-peinh.
190     H_BRTWR = ML_ESLL-BRTWR * 1000.
191     IF ML_ESLL-MENGE NE 0.
192        HELP_NETWR = H_BRTWR / ML_ESLL-MENGE * ML_ESLL-PEINH. "<CH40B/1
>>>>>        <b>MOVE HELP_NETWR TO ML_ESLL-NETWR.                      "<CH40B/1</b>
194 * ml_esll-netwr = h_brtwr / ml_esll-menge * ml_esll-peinh.   "<CH40B/1
195     ENDIF.
Regards,
Abhimanyu.L

Issue with "timing" in Message output of Change PO

Dear Experts,
For change PO, We are facing issue with the Timing in message output of PO.
i.e, For example when we create a PO - the timing in message output is "1"
after executing ME9F, the message turns GREEN - and still the timing is 1.
Change PO : NOW WHEN WE CHANGE A PO, a new entry of Message output appears in "YELLOW"
Here is the issue - Now when we manually change the timing from "3" to "4", initially it appear's "4",
but if u refer the below screenshot - once we save the application i turns back to 3.
any idea - why this is happening.
Thanks in advance.
Regards,
Rohit

Hi,
1st make sure which Dispatch time you want for your PO layout and restrict changing dispatch time manually in PO.
Now use t.code:NACE, with application EF for your PO message type, Keep Dispatch time 4 in ‘Default values’ TAB and select check of “CannotBeChanged” in Basis Data TAB and save.
Maintain message condition record in t.code:MN04 with PO message type and keep Dispatch time 4.
Now create PO , try to change Dispatch time and see how system behave!
Regards,
Biju K

Issue when changing a PO: it creates a new output record automatically

Hello,
The goal is to prevent that a new output record is automatically attached to a purchase order after a change has occurred.
Current situation:
Create a PO for holding and an output record is created for output type ZHP1.
Release PO.
Print the PO in ME9F.
Change the condition record in MN05 and change the language of the print to a different language than the one of the supplier.
Change the PO by adding some header text, the system adds a second output on the purchase order in the language of the cond record.
This should not happen.
Any idea how to achieve this goal rather via customizing than new implementation/changing the SAP standard code!
Thank you in advance.
Aydin

Hi, I'm working with Aydin on this issue.
It creates the second message on the PO and if processed via ME9F then it prints.
But we dont want even that the second output gets created.
We do not work with version management so changes to PO do not create second message.
This second message comes up because language code has been changed in MN05 (one time change) after the first print.
System sees that first message on PO is with language A and now condition record is with lang B.
So If I change any little thing on the PO just to trigger message redetermination, it attaches a second output in the lang B.
If I dont change language code in MN05 and I still do my little change on PO, then it does not attach a second output message (which is good for us)
I thought the only way out is to write a requirement program that would check that if a message already exists on the PO for that output type then dont create a second one. What do you think?
Marc
Edited by: mmlafe on Jan 3, 2012 5:02 PM

Urgent: ABAP Dump when using ME9F

Hi All,
I am using ME9F transaction to re-print POs. I get a short dump stating error "MOVE_TO_LIT_NOTALLOWED_NODATA". This just started happend after we applied the support packs. We are using custom SAP Script form.
Did anyone ever experience this problem before with ME9F or anywhere else.
Any ideas/suggestions will be greatly appreciated.
Thanks in advance.

Check out oSS # 354101
FYI
ME9E: short dump for releases with web releases
Symptom
If messages of JIT delivery schedules and forecast delivery schedules are issued with web release functions in Transactions ME9E, a short dump is generated, if print-dependent data is updated.
Additional key words
ME9E, short dump, MOVE_TO_LIT_NOTALLOWED_NODATA, ME_PRINT_PO, print-dependent data
Cause and prerequisites
For function module ME_PRINT_PO, the transfer of parameter DOC is carried out as a reference. As a result, you cannot change internal tables which are transferred with this parameter.
Solution
Set indicator 'Call by value' for parameter DOC of function module ME_PRINT_PO. As a result, the parameter is copied and can be changed.
Source code corrections
Hope thisll give you idea!!
<b>P.S award the points.</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Update termination in Transaction ME9F

Hello MM Guru’s,
I would like to inform you that we are observing update termination in transaction ME9F for a particular user repeatedly in production environment.
Error in Functional Module: RV_MESSAGE_UPDATE
Error Message: WHT type Z4 missing in vendor master XXXXXXXX
When I check in vendor master data Indicator for withholding tax type Z4 already maintained.
It was strange why when users execute transaction ME9F the above updates terminate happens in the system.
I got a similar issue earlier where at that time Indicator for withholding tax type not maintained in vendor master data and I have informed business to maintain and re execute the transaction ME9F.
Request you to help me on this issue as I said this is a repeated one which is occurring for a particular user and I need to fix it by taking your valuable input.
Revert back in case you need any information required from my end.
Cheers,
Kumar S

Hello Bijay
I was asking you about my analysis (2 different users access ME9F for the same PO) done along with ABAPer whether its correct or not.
In your earlier response you have not responded to my analysis instead you are replying me that experts cant access my system.
I very well understand that our Experts cant access my system but they are always helping me for my all issues with their valuable input.
We just wanted to know whether we are deviating from the issue in this case.
I have also checked what other experts like Jurgen/AKPT & Mallinath suggested me and the analysis given below,
To inform experts that we never use custom print program and we are using standard SAPFM06P print program.But the layout is custom according to our business requirement.
Let me know still you need any clarification from my end.
Regards,
Kumar.S

Problem while displaying Purchase order using me9f

Hi All,
I have copied ME9F as ZME9F, and SAPFM06P as ZSAPFM06P (print program of purchase order). Now when I display the PO using ME23n, there is no problem and PO is getting displayed absolutely fine. But When I display the same PO using ZME9F, the vendor address in the PO is getting printed at the item level instead of header level.
The vendor address should be displayed at the top and not at the item level.
When I analysed the code, I found in case of ZME9F AND ME23N, the values of NAST structure and ENT_SCREEN are different. These values are passed as input values to the Function Module ME_READ_PO_FOR_PRINTING.
Please let me know how do I fix this issue, such that vendor address is displayed at the header level instaed of item level.
Thanks !!!

Hi,
First you creat a PO using BAPI_PO_CREATE , once PO is created then you use the FM BAPI_PO_CHANGE and update the condtions in PO. See the code below given.
Fm lt_cond-condition_no = lvc_knumv.
lt_cond-itm_number = gt_output-ebelp.
lt_cond-cond_type = 'FRB1'.
lt_cond-cond_st_no = '020'.
lt_condx-condition_no = lvc_knumv.
lt_condx-itm_number = gt_output-ebelp.
lt_condx-itm_numberx = 'X'.
lt_condx-cond_st_no = lt_cond-cond_st_no.
lt_condx-cond_st_nox = 'X'.
lt_condx-cond_type = 'X'.
lt_cond-cond_value = gt_output-frcst.
lt_condx-cond_value = 'X'.
lt_cond-currency = p_cndcur.
lt_condx-currency = 'X'.
lt_cond-vendor_no = gt_output-frvndr.
lt_condx-vendor_no = 'X'.
lt_cond-change_id = 'I'.
lt_condx-change_id = 'X'.
APPEND lt_cond.
APPEND lt_condx.
CALL FUNCTION 'BAPI_PO_CHANGE'
EXPORTING
purchaseorder = gt_output-ebeln
TABLES
return = lt_return
* poitem = lt_poitem
* poitemx = lt_poitemx
pocond = lt_cond
pocondx = lt_condx.
Thanks.

Printing problem with ME9F

Hi friends ,
When i try to take print out of purchase order through ME9F , no print out is comeing . All the setings are ok . In SP01 it's shows spool request as waiting and some time as error . Please let me know the reason . Is this problem due to condition table ?.
Regards
Raghavendra

Make sure the folowing things,
Are you using right key combination while creating the PO.
Make sure with the BASIS people that did they setup system configurations / drivers / write printers.
Check is it connected to any workflow? if it there findout the tasks at each and every stage it is triggering
verify any thing connected to security issues?
Make sure and recheck the Output determination condition technique key combinations and access sequence you have defined correct?
It should work now

'Print Preview' in Me22n/23n and thru ME9F and PROCESSING STATUS

Hi ,
We are taking print of Purchase Order thru "Print Preview" button available in ME22N / ME23N.
Although the print out is perfect but system is not changing the processing STATUS of message 'output type'.The status remains YELLOW ( processing program has not started yet).
While If I take the print of same purchase order thru ME9F , we are getting the same Print and the status of output type also gets changed to Green " Processed Sucessfully".
Could u pls let me know what is issue at my end.
Regards
Shrey

Dear,
The system always creates a new version when the purchasing document has reached a final state.
This means one of the following processing states:
● Active
If you do not use the document release functionality
● Release completed
If you use the document release functionality
For a new version of a purchasing document to be created, all messages must have also been transmitted.
No new versions are generated for purchase orders that are on hold.
Not every change to an external purchasing document results in a new version. The following changes lead to a new version:
● All print-relevant changes
You define which changes are print-relevant in Customizing for Purchasing under Messages ® Fields Relevant to Printouts of Changes.
● Changes in document assignment
● Changes in address
Address changes result in a new version only if the field ADRC-NAME1 has been defined as a field that is relevant to printouts of changes.
● Changes to master conditions
Changes in master conditions result in a new version only if the field EKPO-NETPR has been defined as a field that is relevant to printouts of changes.
Version Data
You will find the version data:
● In the item details on the Versions tab page in Enjoy purchase requisitions (ME51N, ME52N, ME53N)
● In the header data on the Versions tab page of Enjoy purchase orders (ME21N, ME22N, ME23N)
● Under Header ® Versions in RFQs, conventional purchase orders (ME21, ME22, ME23), contracts, and scheduling agreements.
There you can maintain version data (e.g. reason for change) and complete the version. In addition, the Value change field shows you whether and to what extent the value of a requisition or external purchasing document item has changed in comparison with the previous version.
You can display the change documents for one or more versions by selecting the relevant versions and choosing Display Changes.
Please check accordingly.
Regards,
Rahul.

PO printout issue

Hi,
I have a pecliar issue with PO printout,
User has raised 7 POs at a time and 6 POs he is able to take printout but the but one PO for which neither print preview is not visible nor able to take Printout.Even in ME9F Particular PO get displayed but is not printing,We see no problem with configuration,No problem with SMARTFORM,No message is generated in process log.Our ABAPer couldnt trace the issue .
what could be the problem?
Regards
R.S.Nambi

Hi,
Go in PO change mode and again assign new output message type NEU or may be what ur suing and again try it compare which output message type u have assign to toher PO for which u have got proper print out.
regards,
zafar

Re-issue PO Output

Hi All,
I have an output setup (email) in the PO. When the PO gets created we have conditions setup in MN04/MN05/MN06 to release it automatically. Does anyone know of a way to re-issue the output in MASS (maybe 20 PO's) after the output has already intially been sent.
I do know that in my output in configuration, I can setup the PO to release upon changes. However, we do not want to do this for every PO. I have also looked at transaction ME9F, but do not see a way to release the email output again.
Any suggestions would be appreciated.
Thanks,
Mark

Hi There
If it is only for the selected POs and not to do trigger from ME22n,
You can do the folllow
1. Me9f
2.Processing Status-1
3.Provide the list of PO doc number
4.Execute it
5.Select all and Click on the message details and Select the output types and Click on the repeat output
6.Save
7.Back to the main screen and with the Processing Status-0, execute it, all the POs can be output again
Thanks
Senthil P

Massdeletion of messages in ME9F

Hi all
We have a lot of messages in ME9F. We want to delete those messages but unfortunately we haven't found a way how we perform a mass deletion in ME9F. The only way is to click on each message then go to "message details", click on the message and delete it here. It is no fun to do that for thousands of messages.
Does anyone have an idea how we can delete or archive all messages in ME9F?
Thanks in advance and regards
Marco

SAP has a report for deletion: RSCLNAST
However, please read the data management guiide, usually NAST records get archived together with documents that get archived thru data-archiving. e.g. PO messages with archiving object MM_EKKO
SAP has issued a clear warning in the data managment guide that records from NAST shall not be deleted as your data are not consistent anymore, and strongly recommends to use data archving.

Print with ME9F or SP01 for different PO document type

Fiends,
I have copied a PO document type to ZNB and I am unable to see the documents in ME9F or SP01 inspite of maintaining the following. But I can see the print preview
With the similar settings document Type NB is working fine in ME9F
Output Type NEU
Key Combination Purchasing Output Determination Document Type
Document Type ZNB
Function VN
Medium 1
Date Time 3
Language EN
Communication
Output Device LP01
Print Immediately is Checked
Sap Cover Page Do not print
Assigned device to Purchase group
Defined Text for messages for this PO type too
Friends please give me solution for this It is very very critical.
Regards

Sorry guys for confusing all of you. The issue was with the release procedure..the POs were not released... inspite of the release button showing "released"... I did not check the status..
hence closing this thread
Thanks

Parallel developments - Version Management issue

Hi all,
My project is going into its enhancement phase and we intend to have a parallel development environment. Dev1 is for maintenance of the Production system, Dev2 for the new enhancement project.
Dev 2 is a client copy of the QA1 environment, as the data there is cleaner than Dev1. Eventually, once the enhancement has gone live, Dev 2 will be the overall Dev system.
My question: Version management is only stored in the source client, that is, Dev 1. How can we sync up the version management histories of Dev 1 and Dev 2. The client is concerned due to audit reasons.
Thanks!

Hi
Here the client doesnt want to use Me9f for output of the message. So the issue is how to get the output done from me21n and get the version updated from Version"0" to Version"1".
for this maintain the Message despatch time as 4 - Send immediately when saving the application Instead of 3 in the message condition record
This will process the message once the PO is relased & saved
Version managemnt is effective only if the existing messages are processed, if the message is not processed then version will not change in the PO.
Thanks & Regards
Kishore

Call Transaction BDC for ME9F in Background

Hi All,
I am posting data to ME9F transaction by using CALL TRANSACTION Method. This runs good in foreground but when i try to run this in the background its not posting the data.Could you please let me know any solution how we can resolve this issue. Thanks in advance.
Regards,
Suresh

According to OSS note #708037:
When transaction ME9F is called in a program with a batch input file, the messages are output to the spool even when they had to be deleted according to the batch input information. This occurs only when the program is called in the background.

ME9F Issue

Similar Messages

Maybe you are looking for