Print PO Form before Release PO

Hi Expert,
I have some problem Print PO Form.
PO cannot print automatically before release PO. (Not release yet)
How can I do ?
Thanks,

Hi,
Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.
Regards ,
Rahul.

Similar Messages

Print of PO Before release

Dear All,
Please help me in one scenario.
My client want PO print before release.
He want to take print of po before release so that he can bargain with vendor & make changes accordinglly before release.
Actually he doesn't want to release the po again & again.
Please help me out
Regards
SANTOSH KADAM.

Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.

Req:Print the PO before release

Hi all,
My requirement is to print the po before release.I have searched for exits/badis but could not find any.
Can anyone help me out how to print the PO before release

Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.

[FormsCentral] Is there any way to allow respondents print filled form before submitting

hi I want my respondents to print form (which they have already filled) before they submit the form.
Is there any way to do that?
Thank you.

If people are filling up the PDF version of your form they can print (and save) from Adobe Acrobat or Adobe Reader before (or after) they submit.
If people are filling up the online (web) version of your form then there is no way to print the whole form beside printing each pages manually from your browser's print functionality.
Gen

Print PO before release

I've implemented the PO release strategy, and I think the SAP standard is not allow print PO before released. I would like to know is it possible to print a termporary PO (another sapscript form) before Po released. Thanks!

Hi,
Yes you can print the PO before release . For that in release strategy against the "Release Indicator" tab see the check box against the colomn"Released". If the box is checked against the final release indicator ,than uncheck it and check the same against the first Release indicator (Blocked). This will allow yoy to print out the PO in blocked state also. But as per standard we do not follow this practice.
Dhruba

PO Printing Before Release

Hi All,
Please let me know, would there be any possibility to get a print of PO before release with release strategy applied to it,
Coz, in my one of the scenario its happening so, and i want to know what would be the probable reason for that,
Regards,
Romesh

Hi All,
Does it depend upon what we maintain in Condition record(MN05), DATE/TIME to 4: Print immediately!
Condition in my case is PO is not yet released by release strategy but its still printing, can it be because of above condition record maintained,
Regards,
Siddaram

Printing the form

I would like to be able to print the form before I get all the responses. Is there a way to print the form? I tried but it is too big for the page. I changed the font size but still can't get it to print.
Thanks.

With a paid account you can save to PDF and print the PDF file.
Randy

Printout of schedule agreement before Release

hi all,
i have created release strategy for schedule agreement at three level EX, MM & GM, problem is that i want to print schedule agreement number thru ME9l after releasing it from EX level. can anyone please tell me that is it possible to print schedule agreement before releasing from all three EX, MM & GM?
if yes then how? or plzz tell me if any other option to print the same.
regards saurabh.
Edited by: saurabh srivastava on May 5, 2009 12:20 PM

If your strategy is set up so that all three levels must release the agreement before it is final released I do not believe you can generate a printout.
Regards

Is there any possiblity to not to take the print out before release of PO

Is there any possiblity to not to take the print out before release of PO.
Please give some inputs to set up this in system.

Hi,
Thank you for your reply with kindness.I will appreciate your help.
I found nothing like what you have mentioned .Please find the programme details in my system.Please help in this reagrd.
FUNCTION EXIT_SAPLMEDRUCK_001.
""Lokale Schnittstelle:
*"       IMPORTING
*"             REFERENCE(IX_DRUVO) TYPE DRUVO
*"       EXPORTING
*"             REFERENCE(EX_RETCO)
*"       CHANGING
*"             REFERENCE(CX_DOC) TYPE MEEIN_PURCHASE_DOC_PRINT
*"       EXCEPTIONS
*"              NO_OUTPUT
INCLUDE ZXM01U04 .
ENDFUNCTION.
Even-- nothing is avaialble in Include programme also.Please help in this regard.
What is my further action to this.

Print of work order before release

Hi,
Is it possible to print a work order before releasing it. What customization/changes can be done to do this ?
Regards,
Vivek

You can do that using standard t-code BS22.
After calling t-code BS22 double click on system status I0001 - CRTD – Created.
Then search for, so called business transaction ‘RMDR - Print Order’ and choose function Allowed.
I have just done it in my sandbox and now I’m allowed to print shop papers for work orders in status CRTD but as per default shop papers should be printed in REL status please analyze possible impact before changing anything in BS22.

Get number of pages of adobe form before printing

Dear Experts,
I want to get number of pages adobe form will print before printing the form.
Please suggest.

Hello Sagar,
Without executing the generated Function Module, it is not possible to get the page count of a form in driver program because the generated FM itself is responsible to execute the whole layout and determine the number of pages in the PDF output. The below screenshot shows the number of pages in the structure /1BCDWB/FORMOUTPUT of generated FM after the generated FM is executed successfully.
I really don't know why you need the number of pages before calling the generated FM. But if you still need it, then you might need to call the whole FM cycle twice( FP_JOB_OPEN , Generated FM, and FP_JOB_CLOSE ).
1) First time while calling the FM FP_JOB_OPEN, you need to modify the contents of SFPOUTPUTPARAMS structure. Send the blank values in fields GETPDF, REQNEW and REQIMM, and send the "X" in fields NOPREVIEW, NOPRINT and NOARCHIVE and 000 in field COPIES.
The reason for doing this is, we do not want actual PDF output. We only want to determine the number of pages.
2) Now execute the generated FM . You will get the number of pages in the structure /1BCDWB/FORMOUTPUT-PAGES as shown in screenshot above.
3) Now call the FM FP_JOB_CLOSE as usual.
4) Again call the FM FP_JOB_OPEN. This time you again need to modify the contents of SFPOUTPUTPARAMS structure reversely. Send the "X" in fields GETPDF, REQNEW and REQIMM, and send the blank values in fields NOPREVIEW, NOPRINT and NOARCHIVE and 001 in field COPIES.
This time we need the actual PDF output.
5) Now do the required processing with previously fetched number of pages before calling the generated FM.
6) Now call the FM FP_JOB_CLOSE as usual.

How to print the script before realasing?

how to print the script before realasing?

Do you want to see the output of your SAPscript??and print it?? before you release.
Then goto NACE tcode and configure your script.
Example :
Goto Transaction NACE --> Select Application V1(Sales) --> Click on Output Types --> Select the output type as BA00 (as generally BA00 is the output type associated with Sales Order ) --> Double click on the Processing Routines folder on the left and it will display the Form name and the corresponding driver programs name.
Goto tcode VA03, and display the output from menu and do your printing.
Close the thread once your question is answered.
Regards,
SaiRam

Print multiple forms between FP_JOB_OPEN and FP_JOB_CLOSE

I am aware, that there are questions regarding "Printing Multiple forms", but I didn't find answers there.
Still my system is not working as expected:
1. FP_JOB_OPEN is called
2. the generated Adobe Forms function is called multiple times
3. FP_JOB_CLOSE is called
This program doesn't deliver all the pages, but just the first call. How shall I solve this problem?
(Coding should work anywhere with copy-pase.)
data: fm_name           type rs38l_fnam,
      fp_docparams      type sfpdocparams,
      fp_outputparams   type sfpoutputparams.
parameters: p_fpname type fpname default 'FP_TEST_02'.
* Get the name of the generated function module
call function 'FP_FUNCTION_MODULE_NAME'
exporting
    i_name     = p_fpname
importing
    e_funcname = fm_name.
* Sets the output parameters and opens the spool job
call function 'FP_JOB_OPEN'
changing
    ie_outputparams = fp_outputparams
exceptions
    cancel          = 1
    usage_error     = 2
    system_error    = 3
    internal_error = 4
    others          = 5.
* Call the generated function module
call function fm_name.
* SECOND CALL ****************************
call function fm_name.
* Close the spool job
call function 'FP_JOB_CLOSE'
*    IMPORTING
*     E_RESULT             =
exceptions
    usage_error           = 1
    system_error          = 2
    internal_error        = 3
    others               = 4.

Hi ZSOLT,
In order to call the form multiple times please do the following,
1) Just before your FP_JOB_OPEN you need to pass the output parameters (good practice). You can also set other parameters as well (for example nodialog, preview, copies., etc)
CLEAR fp_outputparams.
fp_outputparams-dest = 'PDF1'.      "Default pdf printer
fp_outputparams-reqnew = 'X'.       "New spool request
Now call your FM FP_JOB_OPEN with the above output parameters.
2) Usually this step is processed in a loop. (getting your interface data into a internal table and then looping at it)
But here I am enhancing your example code.
In order to trigger the form multiple times you need to change some input data to the form (for example I have changed date and time below in the prepare test data sections) so that the call function fm_name gets regenerated every time there is new data
data l_datatypes       type sfpdatatypes.
prepare test data
l_datatypes-char = '#'.
l_datatypes-string = 'Auf geht''s! '.    "#EC NOTEXT
l_datatypes-numc = '42'.
l_datatypes-dec = 0 - ( 12345 / 7 ).
l_datatypes-fltp = 0 - ( 12345 / 7 ).
l_datatypes-int = 4711.
l_datatypes-curr = 0 - ( 12345 / 7 ).
l_datatypes-cuky = 'JPY'.       " no decimals
l_datatypes-quan = 12345 / 7.
l_datatypes-unit = 'DEG'.       " 1 decimal
l_datatypes-date = '20040613'.
l_datatypes-time = '100600'.
l_datatypes-lang = sy-langu.
FIRST CALL ****************************
Call the generated function module
CLEAR fp_docparams.
fp_docparams-langu = 'EN'.
fp_docparams-country = 'US'.
call function fm_name
    exporting
      /1bcdwb/docparams        = fp_docparams
      datatypes                = l_datatypes
      mychar                   = l_datatypes-char
     mybyte                   =
      mystring                 = l_datatypes-string
     myxstring                =
      mydate                   = l_datatypes-date
      mytime                   = l_datatypes-time
      mynum                    = l_datatypes-numc
      myint                    = l_datatypes-int
      myfloat                  = l_datatypes-fltp
      mypacked                 = l_datatypes-dec
IMPORTING
    /1BCDWB/FORMOUTPUT       =
prepare test data
l_datatypes-char = '#'.
l_datatypes-string = 'Auf geht''s! '.    "#EC NOTEXT
l_datatypes-numc = '42'.
l_datatypes-dec = 0 - ( 12345 / 7 ).
l_datatypes-fltp = 0 - ( 12345 / 7 ).
l_datatypes-int = 4711.
l_datatypes-curr = 0 - ( 12345 / 7 ).
l_datatypes-cuky = 'JPY'.       " no decimals
l_datatypes-quan = 12345 / 7.
l_datatypes-unit = 'DEG'.       " 1 decimal
l_datatypes-date = '20100913'.                 "You need to change your data in order it to trigger a new form with the new data.
l_datatypes-time = '10700'.                        "You need to change your data in order it to trigger a new form with the new data.
l_datatypes-lang = sy-langu.
SECOND CALL ****************************
Call the generated function module
CLEAR fp_docparams.
fp_docparams-langu = 'EN'.
fp_docparams-country = 'US'.
call function fm_name
    exporting
      /1bcdwb/docparams        = fp_docparams
      datatypes                = l_datatypes
      mychar                   = l_datatypes-char
     mybyte                   =
      mystring                 = l_datatypes-string
     myxstring                =
      mydate                   = l_datatypes-date
      mytime                   = l_datatypes-time
      mynum                    = l_datatypes-numc
      myint                    = l_datatypes-int
      myfloat                  = l_datatypes-fltp
      mypacked                 = l_datatypes-dec
IMPORTING
    /1BCDWB/FORMOUTPUT       =
Close the spool job
call function 'FP_JOB_CLOSE'
   IMPORTING
    E_RESULT             =
exceptions
    usage_error           = 1
    system_error          = 2
    internal_error        = 3
    others               = 4.
I have tested the above code and I am getting multiple forms.
Please try on your end and let me know if it works.
Thanks
Raj

Printing a form

Hi folks,
I had an question, related to printing the form using sapscript. I am printing a sapscript form using two printers. The first one is HPLJ4000 : HP Laserjet 4000   and the model is Dell Printer and using this printer the form is printing fine.
However when I print using another printer HPLJ4000 : HP Laserjet 4000 but a different model HPLJ 2100TN some of the data is not printing in the right font size. The font I am using is HELVE and I believe it is not recognising it.
I do not know how to work on the issue, asked the Basis guy too he has no clue about it.
Any thoughts or ideas will be helpful?
Thanks,
Sk

Hi
See this OSS notes
OSSNote:960341
Symptom
In some device types (e.g HPLJ4, HPLJ5) you experience non-uniform character spacing in the PDF document after the PDF conversion of SAPscript or Smart Forms documents, using HELVE or TIMES fonts. You want to know the reason.
Other terms
CONVERT_OTF, SAPscript, Smart Forms
Reason and Prerequisites
The problem is not due to an error in the PDF converter but due to the fact, that the printer font, underlying the device type (e.g. Univers or CG Times in PCL-5 device types), is not available for the PDF converter and is either not available in Adobe Reader. The PDF converter has to try to simulate the layout of the printer font by means of a font which is predefined in Adobe Reader. This is done by assigning the letter widths of the printer font to the font used in Adobe Reader.
The PDF file contains a table with letter widths, used by Adobe Reader in the output of text, for each used printer font (except PostScript fonts).
Example:
%Charwidth values from HP4300 HELVE 060 normal
/Widths
[ 278 333 500 633 633 1000 758 333 333 333 633...
Adobe reader converts this width table, by modifying the space between each character, so that the specified letter width (= space between the current and the next letter) is kept.
This 'Simulation' of printer fonts results in the sometimes visible irregular spaces in PDF.
The PDF converter always uses the Helvetica Adobe PostScript font for the display of HELVE and the Times Roman Adobe PostScript font for the display of TIMES. However, for these Adobe PostScript fonts, Adobe Reader often uses a Windows TrueType font, which differs slightly from the original PostScript font.
Solution
Workaround: Use the POST2 PostScript device type or the PDF1 PDF device type for the PDF conversion of documents in the Latin-1 character set. They both use the Adobe PostScript fonts Helvetica or Times Roman for the HELVE/TIMES printer fonts.
Header Data
Release Status: Released for Customer
Released on: 30.06.2006 12:44:06
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Header Data
Release Status: Released for Customer
Released on: 22.08.2005 09:57:20
Priority: Recommendations/additional info
Category: Customizing
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
BC-SRV-SSF Smart Forms
<b>Reward points for useful Answers</b>
Regards
Anji

Is it possible to print a form in APEX 2.1?

Hi,
Is it possible to print a form in APEX 2.1? I'm able to export a report in cvs, but not a form.
Thanks.

If you're just looking to export a single row via CSV, then yes, you can add that functionality to your Form page in any release of APEX.
Have a look at a blog post I made quite some time ago:
http://spendolini.blogspot.com/2006/04/custom-export-to-csv.html
Using this, you could limit the query to only bring back the row that is displayed in the form.
Thanks,
- Scott -
http://spendolini.blogspot.com
http://www.sumneva.com

Print PO Form before Release PO

Similar Messages

Maybe you are looking for