ME9F Trial Printout - prob in script

Hi Friends,
I have one prob in me9f transaction, Their is one trial printout button and one 'z'form script is attched to
it , I done one modification in the same that on function code of trial printout button '9DPR' i write one code in script   IF &SY-UCOMM& = '9DPR'
                  Disclaimer- This is Draft print out and should not be treated as legal document.
          ENDIF.
when we click on trial printout button,this line is comming only when when we go to se71 and put activate debugger same form is call.
but if we click on trial printout button without activating debugger this line is not comming in printout.but form attached is same.
so pl help me for the same, because user directly click on trial printout button he will get the output.

Hi!
i think there is a commit problem in your program.
you can use after modification this code as the data modified is not updated till the time u again process it..
commit work.
wait up to 10 seconds.
i hope this solves your problem.

Similar Messages

ME9F Trial printout

Hi,
When I use the button trial printout in ME9f, the purchase order is sent auto-matically to the buyer.
I want only a preview of the order and not send it to the supplier.
Somebody could tell me where is the mistake?
Maybe it's in the programm but I don't know where, I just know that the button Print preview is the code function 9DPR.
Thanck's for your help.
Kari

hi,
sorry please ignore my previous mail
Hi,
Go to ME9F enter the purchase order
to see the print review click the DISPLAY MESSAGE output where you can see the preview
trial output is for taking the print out (or ) sending p.o to the vendor by E mail
G.Ganesh Kumar

Looking for ACE Probe TCL script specific for LDAPS

Hello Everyone,
I have searched the forum, and i am having difficulty finding an example of how to modify the LDAP TCL probe from port 389 to secure LDAP port 636.
Could someone kindly point me or provide me the modified TCL script if you happen to have it.
During my search I also found a config that someone had provided, which contained the following probe:
probe tcp LDAPS_Probe
port 636
probe tcp LDAP_Probe
port 389
I was trying to figure out if this a modified TCL script for LDAP or modifed TCP TCL script specific for port 636.
This is how I applied the script for LDAP port 389.
script file 1 LDAP_PROBE
probe scripted LDAP_PROBE_389
interval 5
passdetect interval 30
receive 5
script LDAP_PROBE
serverfarm host SF-LDAP-389
description SF LDAP Port 389
predictor leastconns
probe LDAP_PROBE_389
rserver LDAP-RS1-389
inservice
I will be more than glad to provide you any additional information that you need.
As always thanks for your input.
Raman Azizian
SAIC/NISN Network services

normally you would engage a TCL developer or ciso advanced services to develop a custom script for anything other than what Cisco provides in canned scripts. If you are comfortable with tcl you can do it yourself. Here is an example of the LDAP script modified to include initiation via ssl. default port is 389 when you implement you would specify 636.
#!name = LDAP_PROBE
# Description:
#    LDAP_PROBE opens a TCP connection to an LDAP server, sends a bind request. and
#    determines whether the bind request succeeds. LDAP_PROBE then closes the
#    connection with a TCP RST.
#    If a port is specified in the "probe scripted" configuration, the script probes
#     each suspect on that port. If no port is specified, the default LDAP port 389
#     is used.
# Success:
#   The script succeeds if the server returns a bind response indicating success
#    (status code 0x0a0100) to the bind request.
#   The script closes the TCP connection with a RST following a successful attempt.
# Failure:
#   The script fails due to timeout if the response is not returned. This
#    includes a failure to receive ARP resolution, a failure to create a TCP connection
#    to the port, or a failure to return a response to the LDAP bind request.
#   The script also fails if the server bind response does not indicate success.
#    This specific error returns the 30002 error code.
#   The script closes any attempted TCP connection, successful or not, with a RST.
# PLEASE NOTE: This script expects the server LDAP bind response to specify length
#   in ASN.1 short definite form. Responses using other length forms (e.g., long
#   definite length form) will require script modification to achieve success.
# SCRIPT version: 1.0       April 1, 2008
# Parameters:
#   [DEBUG]
#      username - user login name
#      password - password
#      DEBUG        - optional key word 'DEBUG'. default is off
#         Do not enable this flag while multiple probe suspects are configured for this
#         script.
# Example config :
#   probe scripted USE_LDAP_PROBE
#         script LDAP_PROBE
#   Values configured in the "probe scripted" configuration populate the
#   scriptprobe_env array. These may be accessed or manipulated if desired.
# Documentation:
#    A detailed discussion of the use of scripts on the ACE is included in
#       "Using Toolkit Command Language (TCL) Scripts with the ACE"
#    in the "Load-Balancing Configuration Guide" section of the ACE documentation set.
# Copyright (c) 2005-2008 by Cisco Systems, Inc.
# debug procedure
# set the EXIT_MSG environment variable to help debug
# also print the debug message when debug flag is on
proc ace_debug { msg } {
    global debug ip port EXIT_MSG
    set EXIT_MSG $msg
    if { [ info exists ip ] && [ info exists port ] } {
     set EXIT_MSG "[ info script ]:$ip:$port: $EXIT_MSG "
    if { [ info exists debug ] && $debug } {
     puts $EXIT_MSG
# main
# parse cmd line args and initialize variables
## set debug value
set debug 0
if { [ regsub -nocase "DEBUG" $argv "" argv] } {
    set debug 1
ace_debug "initializing variable"
set EXIT_MSG "Error config: script LDAP_PROBE \[DEBUG\]"
set ip $scriptprobe_env(realIP)
set port $scriptprobe_env(realPort)
# if port is zero the use well known ldap port 389
if { $port == 0 } {
    set port 389
# PROBE START
# open connection
ace_debug "opening socket"
set sock [ socket -sslversion all -sslcipher RSA_WITH_RC4_128_MD5 $ip $port ]
fconfigure $sock -buffering line -translation binary
# send a standard anonymous bind request
ace_debug "sending ldap bind request"
puts -nonewline $sock [ binary format "H*" 300c020101600702010304008000 ]
flush $sock
# read string back from server
ace_debug "receiving ldap bind result"
set line [read $sock 14]
binary scan $line H* res
binary scan $line @7H6 code
ace_debug "received $res with code $code"
# close connection
ace_debug "closing socket"
close $sock
# make probe fail by exit with 30002 if ldap reply code != success code 0x0a0100
if { $code != "0a0100" } {
    ace_debug " probe failed : expect response code \'0a0100\' but received \'$code\'"
    exit 30002
## make probe success by exit with 30001
ace_debug "probe success"
exit 30001

ACE probe TCL script database

Hello everyone, okay?
I was thinking of a possibility to use my ACE to monitor a database, in this case a MySQL database Today I use a TCP probe, monitoring the port, but I would go one step further and try to make a connection in the DATABASE.
I would like to see the possibility of a guideline in creating a TCL script to make a simple connection to a database.
The idea is to try to make a connection in a database, run a query / select on any table just to validate its functionality and not just checking if the port is responding.
I do not know how complex it is or what would be my pre -requisites required, but any help would be welcome.
I thought about using an HTTP probe to make this validation and use a web page making the connection to the database, but it ended up creating another layer and if there is any problem in web service, the database would be affected indirectly.
Thank you. All suggestions are welcome.

Hi Plinio,
I cannot see any support for testing authentication, SQL queries or connections to a database that is supported directly in TCL at this time.
Here is the TCL guide that expalains the supported commands ( there is a HTTP example probe at the bottom )
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA4_2_0/configuration/slb/guide/script.html
Beyond a TCL TCP probe to the port to test the listener is running, I believe your suggestion of a HTTP TCL script is probably the most accurate way to check the integrity of the database. You could write code to set a certain response to all types of failure scenarios and on the ACE you could then use a HTTP TCL script to parse the response from the web server to identify exactly what has failed in your database and act accordingly.
cheers,
Chris

Trial download probs!!!

Hi All
I downloaded a trial version of Productio premium a week ago and all was fine, I then decided to try Master collection so started the download process It said prod premium was already there so I didn't tick those boxes and the download completed with no probs... I then had probs with prod premium so I decided to uninstall the lot and just re install master collection as a whole... Thats where the probs began!? I keep getting the 'error code 105' I have tried re installing Adobe installer but I get the same... I looked into installer to see if there were any others already in the queue (as suggested) and there isn't ... I am running Windows 7 64bit
Any help!!!?
regards
Dean

Troubleshoot Adobe Download Assistant
Mylenium

Sales invoice printout probs

hi experts.
we are 3 plants for our concern and we are prepared the sales invoice through t-code j1ip , when we are shifted the materials from one plant to another plant ie inter-plant .it could not print the customer address in the to block. of sales invoice .but when we are shifted the material to other external concern. it could printed the customer address in the to block..
pls somebody rectify this prob.
regards
surender

hi jignesh ..
basically am a abaper. i knew this is the smartform/sapscript issue. in the top left of the sales invoice the customer address should be print. but it could not be printed while we use the t-code j1ip.. plz resolve this.
and one more ques. is how to retrieve the abap and smartforms/sapscript program for the particular sales invoice.
i think u understood what am ask..?
see our plant name is x. and i want to shift the materials to x1.
x1,
2/3 cambridge road,
banglore.
the above address should be printed in the top-right corner of the delivery challan *** invoice.
regards
surender

Prob in script

Dear All,
I am working in Script and my Amount total is coming in the format like 82,935,180.00. Now I want Amount total should come in the format like 8,29,35,180.00.
How I will make that changes.
Please help me.
Thanks & regards,
Abhay.

Hi
This can be handled using:
SET COUNTRY
or With the help of User Profile.
Regards,
Sree

Report ME9F

Hi experts,
I need to print any PO in ALV through ME9F ( trial printout button ) even if PO is not yet released; is it possible ?
and if yes, how can I do ?
Thanks a lot in advance,
regards.
Marco

hi,
You can't print out if the PO is not released, you can only see the print preview of it...but can't take print out...
You have to release it first..
Regards
Priyanka.P

Two spool getting generated for a single SAP script

Hi ABAPers,
I have a SAPscript development. This is a PO form for India. When I do a "Trial printout" in ME9K I see that two spools are generated. This is my first problem as till last week only one spool was getting generated. Only spool should be generated.
My second problem is that, the second spool which is generated has texts shown in some different language than English (my form only exists in language EN which is the orginal one too). When I debugged this whole thing, on the second run of the debugger (i.e. when the second spool is generated), when the control goes to a text in one of the windows, that text is shown in some other language (in debug mode also). Please note that the standard text is a Global standard text and it exists in around 6 languages.
I guess if only one spool is generated then my second problem would be solved. But then why are 2 spools generated in the first place?
If anyone has came across similar kind of problem please help. Thanks in advance.
regards,
Prakhar

Hi,
Check this..
1. Go to txn. NACE... select application "EF"... then click on "Condition Records" button
2. Select your Output Types...(ex. NEU)....
3. Go to Change condtion Record Screen. Select ur condtion then click on "communication" button..
4. Under Print Output Check the field "Number of Message" if it is 2 then delete it.
Regards
GK.

ME9F Print preview vs Output Message

Dear Expert,
I would like to know that can we add any text on the face of the PO that shows that it is printed from the Trial Printout button, so that user should use the Output button to finally printout the PO?
Thanks for all your kind attention,
Regards,

Yes you can check which button is pressed by inform ABAPER to check global variable
sy-ucom
IF sy-ucomm EQ '9AUS' => Output message
IF sy-ucomm EQ '9DPR' => Trial Printout
Hope these can help you.

My stop script is no longer working in new cs5 - i can't stop my just completed movie

my stop script is no longer working in new cs5 - i can't stop my just completed movie - i also tested the stop command
in test/trial movie and [ action script ] (stop) is not working - is my only resolution to call adobe tomorrow?

i figured out that the text was somehow keeping the stop and other code snippets from working - once i eliminated the text layer, my movie works properly --thxs
yesterday the stop() snippet was not working at all - text was not the problem - ?? there was never an error message - the debug message said that i had no action script.- now all is well -

Photoshop CC 32Bit Script with Dialogs.

http://forums.adobe.com/thread/1336205 I'm Having a problem with Photoshop CC trial 32bit version with scripts that have dialogs not work with my install also posted in general forum. Is it my install I can not believe a bug that bad would ever be released. How do you shoot an error 22 message?

Turned out to be a Preference file MachinePrefs.psp which worked in Photoshop CC 64bit cause CC32bit scripts dialogs not to work go figure. It may have to do with OpenCL support. In CC64bit I used Advance GPU setting and checked it. 32Bit CC I can not check it with mt setup nvidia quadro 4000.

P.O. RELEASE & PRINTOUT DISPLAY

Hi All,
Plz Tell me the procedure of <b>P.O. RELEASE & PRINTOUT DISPLAY</b> in detail....with example...
Thanks & Regards,
<b>Anil Kumar</b>

The aim of this procedure is to replace manual written authorization procedures using signatures
by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system,
thereby marking it with an electronic signature which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing
documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no
provision for item-wise release (i.e. partial approval) in the case of the external
purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the
procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing.
In addition, a class with characteristics must have been created for each document (requisition,
purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for
requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release
Procedure for the relevant documents and in Set up Release Procedure with Classification for
purchase requisitions. Detailed information on classification is available in the SAP Library in the
Cross-Application Components documentation under Classification System, sections CA -
Characteristics [Ext.] and CA The Classification System [Ext.].
This procedure offers a wide range of possible combinations of release criteria.
Should you nevertheless have other requirements, use the enhancement provided
by SAP.
See also:
Operation of Release Procedure w. Classification
1. The characteristic values from a requisition or external purchasing document are passed on
to the classification system.
2. The system checks whether the values correspond with release conditions. If so, it assigns a
release strategy.
3. The persons responsible for the release codes process the document in the sequence
defined in the release strategy.
The following graphic illustrates the process, taking a requisition item that is subject to the
release strategy S4 as an example:
Release strategy S4
PReq.
Work item
Release points
Alternative
1
1
2
2
3
3
4
4 5 Released!
SAPWorkflow
PReq.
Item
data
Passed on to
Classification system
Purchasing group
Vendor
Plant
Value
Material group Metal-1
C
4750
1
$200,000
Characteristic Char. value
XX
X
... XX
= relevant
Changes After the Start of the Release Procedure
The following cases can arise when a purchase requisition or external purchasing document for
which the release procedure has already started is changed:
_ Case 1: Insignificant change that does not necessitate a different release strategy.
_ Case 2: Relevant change that does not necessitate a different release strategy.
_ Case 3: Relevant change that necessitates a different release strategy
In each case, the system issues a message to the user after the change has been made.
Case 1
Instead of 10 tons of Steel 1 at a total price of $100, only 8 tons are needed, at a
total price of $80.
This subsequent change to the document is possible.
The release procedure continues uninterrupted.
Case 2
A user has the authorization for purchase orders valued between $1,000 and
$120,000. Release strategy FS is assigned in this case.
The user has ordered 10 cameras at a price of $1000 each. The release procedure
has already started and the release indicator 01 (free for issue of RFQ) has been set.
The settings made in Customizing for Purchasing for release indicator 01 are such
that the system will issue a warning message if the original PO value is exceeded by
more than 50%.
The user then changes the PO to 100 cameras, causing the PO value to increase by
more than 50%. The system reassigns release strategy FS and issues the warning
message. The user has the following options:
_ Correct the PO, so that the percentage is not exceeded. The release procedure then
continues.
_ No correction to PO. The system then cancels the previous releases and the release
procedure starts all over again from the beginning.
Case 3
An electron beam welding machine assigned to project A is to be subsequently
reassigned to cost center 3. Again, it is not possible to simply go ahead and make
this change. The system will issue an error message. Either the change must be
cancelled, or the release strategy redetermined and the approval procedure
restarted.
Release with Link to Workflow
Use
When you set up the release procedure with classification for purchase requisitions or purchase
orders, you can define a link to the SAP Business Workflow. This is particularly advisable if
employees whose daily duties include tasks other than the approval of requisitions or purchase
orders are involved in the release procedure.
Features
The employee is automatically advised when a release is to be effected. A work item appears in
his or her inbox, which he or she can process directly. When the item is processed, the SAP
release transaction is automatically invoked with the relevant release code.
For more information, refer to MM - Materials Management: Workflow Scenarios [Ext.].
Printout Display:
Outputting Messages
Prerequisites
_ The message output queue must contain messages.
_ The purchasing documents represented by the messages must have been released
(approved).
You can either schedule a background job (RSNAST00), which processes the
message queue at predefined intervals, or initiate outputting directly via the
Purchasing menu. As a rule, you will use the background job to output messages
and only use the manual output facility in exceptional cases (e.g. rush orders).
Outputting Messages in the Background with RSNAST00
1. Choose System _ Services _ Reporting.
2. Enter rsnast00.
3. Define the selection criteria in a variant.
4. Schedule the job.
Outputting Messages Manually
1. Choose <Purchasing document> _ Messages _ Print/transmit.
The message selection screen appears.
2. Enter the selection criteria for the documents to be outputted.
Whether further input fields are available depends on the selected application.
3. Choose Program _ Execute.
The message output queue is displayed.
4. Display output: If you want to print out or fax a document, you can display it first. Select the
desired document and choose Goto _ Display messages.
5. Trial printout: Choose Goto _ Trial printout to check the printing of the document (to see
whether the paper is aligned properly in the printer or to proofread a purchase order before
sending it out, for example). A trial printout has no influence on the processing status of the
document.
6. Select the desired document(s) and choose Edit _ Print/transmit.

Function of health probe timers on CSM

Hi,
we use the following configuration on a csm to monitor a server farm and I'm wondering how exactly the probe timers work.
===
serverfarm sf
nat server
nat client natpool1
failaction purge
real name serv1
weight 1
inservice
real name serv2
weight 1
inservice
probe probe1
probe probe1 script
script LDAP_PROBE
interval 5
retries 2
receive 1
port 389
===
So in my eyes the probes are sent every 5 seconds. When a probe isn't answered within one second it's marked as failed. If two probes are failed (retries 2) the real server is marked as down.
Is this correct?
In a network trace I see a different behaviour: Probes are sent every 5 seconds. If a real server goes out-of-service I see a probe which is not answered and the next probe is sent after 10 seconds (I expected 5 seconds). 5 seconds later the real server is marked down in the switch log.
It would be fine if anybody could help me.
Best Regards,
Thorsten Steffen

Hi,
following the meaning of the parameters:
Router(config-slb-probe)#
interval seconds
Sets the interval between probes in seconds (from the end of the previous probe to the beginning of the next probe) when the server is healthy.
Range = 2-65535 seconds
Default = 120 seconds
Router(config-slb-probe)#
retries retry-count
Sets the number of failed probes that are allowed before marking the server as failed.
Range = 0-65535
Default = 3
Router(config-slb-probe)#
failed failed-interval
Sets the time between health checks when the server has been marked as failed. The time is in seconds.
Range = 2-65535
Default = 300 seconds
Router(config-slb-probe)# open
open-timeout
Sets the maximum time to wait for a TCP connection. This command is not used for any non-TCP health checks (ICMP or DNS1).
Range = 1-65535
Default = 10 seconds
There are two different timeout values: open and receive. The open timeout specifies how many seconds to wait for the connection to open (that is, how many seconds to wait for SYN ACK after sending SYN). The receive timeout specifies how many seconds to wait for data to be received (that is, how many seconds to wait for an HTTP reply after sending a GET/HHEAD request). Because TCP probes close as soon as they open without sending any data, the receive timeout is not used.
When sniffing, you should see a probe each 5 seconds. When a probe fails for the first time, a second probe should be send after 5 seconds. when this probe fails too, the server is put out of service.
That should be the behaviour you should see.
HTH,
Dario

PDF generation about PO

Hello, all.
Anyone can tell me how to generate PO PDF file, thanks.

Hi,
Convert PO to PDF
Go to ME22N -- Messages - select output NEU -- Communication Methods --
Give printer name, Do not select the option "Print immediately". Give some name in "Spool request Name" field. Save the PO.
Then go to ME9F, give the PO number - F8 - select PO & Trial printout (Note: print wonu2019t come out). Then go to SP01 & F8 (Execute). You will get the spool no. for your PO.
Once the spool request number is known
Go to SE38.
Give the program name: RSTXPDF4 or RSTXPDFT4
Execute.
Give the spool number & execute.
The PO will be converted into PDF format.

ME9F Trial Printout - prob in script

Similar Messages

Maybe you are looking for