Contract Output

Dears,
We have created (by copying output type 'NEU') a new message type 'ZNEU' for outline agreements. However it is not showing in ME32K. Any idea why it is not coming?
Thanks,

Hi,
Go to NACE, Go EV there Go to Procedure....
and for RMBEV1.....Assigen your out put here.
Hope Help U !
Regards,
Pardeep Malik

Similar Messages

Purchasing Contract output - form language determination

First, here's a shot outlook on the situation:
The customer created a vendor master, with the communication language German. He then created a contract with that vendor and tried to print it, but the output form came out in German. I checked the message in the contract, and the language was RO, not DE.
The customer then changed the communication language in the vendor master from german to romanian; then he deleted the message in the contract and recreated it, but the language for the form is still german. He told me that when he tries to recreate the message, the default language is still DE and he changes it to RO.
Please tell me why the language is still defaulted to DE. I checked in customizing & the vendor master and I can't find the DE language anywhere.
Thankyou in advance,
Cosmin

HI,
What is the log in language for the user?.
Usually when u need to print PO in different languages two output types are created one for each language .Check in previous what output type is used for german & RO..
DID u check in this node
MM>PUR>MESSAGES>OUTPUTCONTROL>MESSAGE TYPES>DEFINE MESSAGE TYPES FOR PO
Double click on first,select NEU,THEN CLICK ON SEE THE DEFAULT LANGAUAGE.
MURUGAN
Edited by: Murugan mgl on Aug 6, 2009 2:41 PM

Terms and Conditions with a Service Contracts

Hello,
I like to use the Sales Contracts (11.5.10) templates that I created for Sales Quote and Service Contracts. There is a great layout template (XML) for Quoting. I could not find any documentation on how to attach T*Cs to a Service Contract output.
Any help in this direction will be appreciated.

Yes, I did. I had to insert a page break for this. Here is how I have done this
<fo:block break-before="page" >
</fo:block>
Thanks,
Sharmila

Transaction used for maintaining condition record for contract

Hi All,
In one of the issue user is not able to print contract,we have noticed that default printer is set for user.I need to check what condition record is maintained for user.
Can anyone let me know what is the transaction used for maintaining condition record for contract output.
Regards,
Dharmesh

Hi
MN01 Create Message: RFQ
MN04 Create Message: PO
MN07 Create Message: Outline Agreement
MN10 Create Message: Schd. Agmt. Schedul
MN13 Create Message: Service Entry Sheet
MN21 Create Condition: Inventory Mgmt
MN24 Create Message: Shipping Notif.
MN27 Create message: rough goods receipt
MN10 / MN11 - Scheduling Agreement Delivery Schedule
Vijay

SRM Local Contracts - Price Conditions

Hi,
We are trying to extract the price conditions from the SRM Local Contract line items, with the Condition Type, Valid From, Valid To, Amount, Price Unit, Unit. This is to allow us to track the changes in contract prices.
If you have any experience of this, or know which SRM tables we need to be extracting from it would be greatly appreciated! We already have the Contract Header and Line information from CRMD_ORDERADM_H, CRMD_ORDERADM_I, BBP_PDHGP and BBP_PDIGP. Where are the conditions stored? And are there any extractors planned for this in the future? It would be very useful standard content.
Thanks.

Hi
Few BADIs to refer using SE18 Transaction (Please read standard documentation provided by SAP on them )
BBP_IMS_CONTACT Changes the Contract for the E-Mail
BBP_CTR_INIT_UP Contracts and GOAs to SRM
BBP_CHANGE_SF_CTR Change Smart Form for Contract Output
BBP_CND_UI_CTRL BBP Conditions: UI Control
BBP_CTR_BE_CREATE Exit when Creating a Contract in the Backend System
BBP_CTR_INIT_UP BAdI to upload Contracts and GOAs to SRM
BBP_CTR_MAIL_BADI BAdI for Changes Regarding Sending Mails
BBP_CTR_MASS_BADI Implementation of Mass Change Parameters
BBP_CTR_STAT BAdI to enable changes in the contract status
BBP_PROCESS_CTR Process Smart Form with Changed Interface
BBP_QA_REDETERM_CTR Redefine the Contract to be Used (Quota Arrangement)
Please go through these links ->
http://help.sap.com/saphelp_srm50/helpdata/en/58/2a8442a07b0e53e10000000a155106/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/6d/1e8442a07b0e53e10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/fd/dc804258544b76e10000000a155106/frameset.htm
Regards
- Atul

Central Contract sent to Supplier

Hi,
I am working in SRM 7.02,
Creating a Central contract in SRM system and distributing the same to ECC system.
I want to sent the contract to Supplier through mail as RFx ..What are the configuration that needed???
Is there any setting need to be done..
Kindly guide me...

Dear Martin,
Thanks for the response.
But when i click process output button in the contract -> Output.
The below error message is displayed 'Output could not be created; contact your system administrator'.
And is there any way to send automatically to vendor, once the contract is released fully.
Regards,
Tamil.

Smart form modification.(Language requriments)

Hi all,
I have to change the smartform for the language requirements with out changing print program. Here the form ic processed by the Classes and methods. Those r standard.
we have to check the condition i.e pur. org. country and vendor country.
If both are same we have to print the texts in local language.
(see below code for conditions).
For this,
 we have to write a code.
Where we have to write the code in smartform (not in print program)?
Contract Output processing details:
Compare Country of Purchasing Organization with Country of Vendor from the Contract
A. If the Country of Purchasing Organization and Country of Vendor from the CONTRACT are the same, then use local language (ZBBP_FORM_LAYOUT_DET - ZLOCAL)
1. If local language (ZBBP_FORM_LAYOUT_DET - ZLOCAL) is EN then print form layout and print Texts in (ZBBP_FORM_TXT_DET-ZFILE_LOCAL) in English(EN) for the Purchasing organization, Form type and output date between the date range (ZFROM_DATE and ZTO_DATE)
2. Local language (ZBBP_FORM_LAYOUT_DET - ZLOCAL) is not EN and based on Label Language (ZLABEL_LOCAL), Print labels in the required languages and print Texts in (ZBBP_FORM_TXT_DET-ZFILE_LOCAL) in Local language for the Purchasing organization , Form type and output date between the date range (ZFROM_DATE and ZTO_DATE)
B. If the Country of Purchasing Organization and Country of Vendor from the Contract are NOT the same, then use language as non-local language (ZBBP_FORM_LAYOUT_DET - ZNONLOCAL) then print form layout based on Label Language (ZLABEL_NONLOCAL) and print Texts in and print Texts in (ZBBP_FORM_TXT_DET-ZFILE_NONLOCAL) for the Purchasing organization, Form type and output date between the date range (ZFROM_DATE and ZTO_DATE)
Step 2:
Get Texts Names and language where Text Type in ('BILL_TO' ,HEADER, EOP, NOTE,, FOOTER_LT, FOOTER_MID, FOOTER_RT, EODOC, TERM_COND') as per the purchasing Org and Date range, then get Text details of 'Text name' where text id ='ST' as per the language and populated them on the Contract which are stored using transaction code 'SO10'.
Output Processing:
During the Output preview Texts info will be populated as per the latest output of Contract transmitted to the Vendor, the date of last output is fetched from the log table Contract output.
Date format and decimal notation:
Print Date Format (V_T005_BAS-DATFM) and decimal notation (V_T005_BAS-XDEZP) on Contract form, where Country of Purchasing Organization of the Contract is equals to Country ISO code(V_T005_BAS-INTCA)
This is requirement.
Where ew have to impliment the code in smartform?
Can any one help on this?
We r not going to change the classes and methods. (Print program)
Rewards to all.
Thanks,
Anu.

Hi!
You can do this within the Smartform.
You have to define the window in all languages, you wanted to print. Then you can define conditions for the language code. If you set a condition to one of the windows, you have to exclude it from the another.
For example
ZWINDOW_EN - condition language = 'EN'
ZWINDOW_OTHERS - condition language <>'EN'
Regards
Tamá

General questions

hi,
i have some doubts in reports.pls tell the answers.
which contain the details of all name of the programs and forms?
difference between pooled and cluster tables?
what are output types and tcodes?
what are the main events that are used in alv reports?
thanx and regrads
priya

Hi
which contain the details of all name of the programs and forms?
In TNAPR table you will find them.
difference between pooled and cluster tables?
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences,
program parameters or temporary data). Several pooled tables can be
combined to form a table pool. The table pool corresponds to a physical
table on the database in which all the records of the allocated pooled
tables are stored.
Cluster table
Cluster tables contain continuous text, for example documentation.
Several cluster tables can be combined to form a table cluster. Several
logical lines of different tables are combined to form a physical record
in this table category. This permits object-by-object storage or
object-by-object access. In order to combine tables in clusters, at
least part of the keys must agree. Several cluster tables are stored in
one corresponding table on the database.
what are output types and tcodes?
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
OUTPUT EXECUTION TCODES
ME9F - Pur Order Output
ME9A - RFQ Output
ME9K - Contract Output
MB90 - GRN Output
VA02/VA03 - Sales order Output
VF03/VF02 - Invoice output
VL71   - Delivery Output
VT70 - Shipment Output
VL74 - Handling Unit Output
what are the main events that are used in alv reports?
REUSE_ALV_EVENTS_GET
Description
This table tells ALV which events are processed by the caller by CALLBACK.
The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
The table structure contains the fields:
     IT_EVENTS-NAME
Name of the Callback event.
Possible Callback events:
     Action
USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
Process actions on the list
As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
The STANDARD status of the function group SALV should be used as a template for a user-specific status.
As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
     List processing events
IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
TOP_OF_LIST no USING parameter. Information output at the start of the list
END_OF_LIST no USING parameter. Information output at the end of the list
TOP_OF_PAGE no USING parameter
Equivalent to the list processing TOP-OF-PAGE event
END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
Information output at the end of a page. This is only called for printing.
TOP_OF_COVERPAGE no USING parameter
The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
IS_PRINT-NO_COVERPAGE
IS_PRINT-NO_PRINT_SELINFOS
IS_PRINT-NO_PRINT_LISTINFOS
IS_LAYOUT-GET_SELINFOS
The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
END_OF_COVERPAGE no USING parameter
Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
FOREIGN_TOP_OF_PAGE no USING parameter
The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
FOREIGN_END_OF_PAGE no USING parameter
The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
     Internal use only
LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
R_INDEX LIKE SY-TABIX
R_INDEX_ITEM LIKE SY-TABIX
R_INDEX_SUM LIKE SY-TABIX
     IT_EVENTS-FORM
Name of the form routine which should be called in the calling program at the event.
Field_catalog:
Field catalog with field descriptions
2.7.1.     Description
Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
     all fields in this structure are to be output
     the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
Positioning
     row_pos (row position)
value set: 0, 1 - 3
Only relevant if the list output is to be multi-line (two or three lines) by default.
A multi-line list can also be defined by the user interactively if the default list is one-line.
The parameter specifies the relative output line of the column in a multi-line list.
     col_pos (column position)
value set: 0, 1 - 60
only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
Identification
     fieldname (field name)
value set: internal output table field name (required parameter)
Name of the internal output table field which is described by this field catalog entry
     tabname (internal output table)
value set: SPACE, internal output table name
This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
Data Dictionary reference
     ref_fieldname (reference field name)
value set: SPACE, Data Dictionary field name
Name of the Data Dictionary field referred to.
This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
     ref_tabname (reference table/structure field name)
value set: SPACE, name of a Data Dictionary structure or table
Structure or table name of the referred Data Dictionary field.
This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
Reference to fields with currency/measurement unit
Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
     the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
     There is a field in the internal output table which contains the associated unit.
     There is also an entry in the field catalog for the unit field.
(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
The association of a value field to a unit affects the output as follows:
     appropriate decimal places display for the unit
     an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
     an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
     When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
Link to currency unit
     cfieldname (currency unit field name)
value set: SPACE, output table field name
Only relevant for amount columns with associated unit.
Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
     ctabname (internal currency unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Link to measurement unit
     qfieldname (measurement unit field name)
value set: SPACE, output table field name
only relevant for quantity columns with unit link.
Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
     qtabname (internal measurement unit field output table)
value set: SPACE, output table field name
only relevant for hierarchical-sequential lists
Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Column output options
     outputlen (column width)
value set: 0 (initial), n
For fields with a Data Dictionary link this parameter can be left initial.
For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
initial = column width is the output length of the referred Data Dictionary field (domain).
n = column width is n characters
     key (key column)
value set: SPACE, 'X'           'X' = kex field (key field output in color)
Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
     key_sel (hideable key column)
value set: SPACE, 'X'
only relevant when FIELDCAT-KEY = 'X'
Key field which can be hidden interactively.
The key column sequence cannot be changed interactively by the user.
The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
     no_out (field in field list)
value set: SPACE, 'X'          'X' = field is not displayed in the current list.
The user can interactively choose the field for output from the field list.
The user can display the contents of these fields at line level using the 'Detail' function.
See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
     tech (technical field)
value set: SPACE, 'X'          'X' = technical field
Field cannot be output in the list and cannot be displayed interactively.
Field can only be used in the field catalog (not in IT_SORT, ...).
     emphasize (highlight columns in color)
value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = column is colored with the default column highlight color.
'Cxyz' = column is colored with a coded color:
     C: Color (coding must begin with C)
     x: color number
     y: bold
     z: inverse
     hotspot (column as hotspot)
value set: SPACE, 'X'
'X' = column cells are output as hotspots
     fix_column (fix column)
value set: SPACE, 'X'
Not relevant for block lists (output of several lists consecutively)
'X' = column fixed (does not scroll horizontally)
All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
     do_sum (sum over column)
value set: SPACE, 'X'           'X' = a sum is to be calculated over this internal output table field.
This function can also be called by the user interactively.
     no_sum (sums forbidden)
value set: SPACE, 'X'          'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
     input (column ready for input)
Function not available
Format column contents
     icon
value set: SPACE, 'X'           'X' = column contents to be output as an icon.
The caller must consider the printability of icons.
     symbol
value set: SPACE, 'X'          'X' = column contents are to be output as a symbol.
The internal output table column must be a valid symbol character.
The caller must consider the printability of symbols.
Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
     just (justification)
value set: SPACE, 'R', 'L', 'C'
Only relevant for fields of data type CHAR or NUMC
' ' = default justification for this data type
'R' = right-justified output
'L' = left-justified output
'C' = centered output
The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
     lzero (leading zeros)
value set: SPACE, 'X'
Only relevant for fields of data type NUMC
ALV outputs NUMC fields right-justified without leading zeros by default.
'X' = output with leading zeros
Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
     no_sign (no +/- sign)           Only relevant for value fields
value set: SPACE, 'X'     'X' = value output without +/ sign
     no_zero (suppress zeros)           Only relevant for value fields
value set: SPACE, 'X'          'X' = suppress zeros
     edit_mask (field formatting)
value set: SPACE, template
template = see documentation of WRITE formatting option USING EDIT MASK template
The output conversion conv can be made by template = '== conv'.
Texts
The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
The 'long field label' is also used in display variant definition, sort, etc. popups.
     seltext_l (long field label)
     seltext_m (medium field label)
     seltext_s (short field label)
     reptext_ddic (header)
analogous to the Data element maintenance 'Header'
The specified text is not necessarily output in the list, an optimum among all texts is sought.
     ddictxt (specify text)
value set: SPACE, 'L', 'M', 'S'
You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
Parameters for program fields without Data Dictionary reference
see also 'Text' parameters
     datatype (data type)
value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
Only relevant for fields without Data Dictionary reference
Program field data type
     ddic_outputlen (external output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
     FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
     FIELDCAT-INTLEN = n
see also the documentation of the parameter FIELDCAT-INTLEN
n = external format field output length
The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
     intlen (internal output length)
value set: 0 (initial), n
Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
Prerequisites:
     FIELDCAT-EDIT_MASK = '==conv'
see also the documentation of the parameter FIELDCAT-EDIT_MASK
     FIELDCAT-DDIC_OUTPUTLEN = n
see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
n = internal format field output length
     rollname (data element)
value set: SPACE, Data Dictionary data element name
F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
When F1 help is called for this field, the documentation of the specified data element is displayed.
If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
Others
     sp_group (field group key)
value set: SPACE, CHAR(1)
Field group key.
Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
     reprep (Report/Report interface selection criterion)
value set: SPACE, 'X'
Prerequisites:
     The system contains the Report/Report interface (function group RSTI, table TRSTI)
     Parameter LAYOUT-REPREP = 'X'
(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
2.7.2.     Default
     The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
     fieldname
     ref_tabname
Notes:
ALV gets the remaining information from the Data Dictionary.
If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
Priority rule:
Entries in the field catalog have priority over differing entries in the Data Dictionary.
     The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
     fieldname
     outputlen
     datatype
     seltext_s
     seltext_m
     seltext_l
Notes:
F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
Reward points for useful Answers
Regards
Anji

In which table scripts and smartforms are stored

in which tables scripts and smartforms are stored
eg scripts in tadir.

Hi this may be of some help.
SD
SALES ORDER/ENQUIRY/QUOTATION
Output type         : BA00
ScriptForm Name     : RVORDER01
Driver Program Name : RVADOR01
smartform name
DELIVERY NOTE
Output type         : LD00
ScriptForm Name     : RVDELNOTE
Driver Program Name : RVADDN01
smartform name      : LE_SHP_DELNOTE
Smartform Driver Pgm: RLE_DELNOTE
INVOICE
Output type         : RD00
ScriptForm Name     : RVINVOICE01
Driver Program Name : RVADIN01
smartform name      : LB_BIL_INVOICE
Smartform Driver Pgm: RLB_INVOICE
MM
PUCHASE ORDER/RFQ/CONTRACT
Output type         : NEU
ScriptForm Name     : MEDRUCK
Driver Program Name : SAPMF06P
smartform name      : /SMB40/MMPO_L
smartform driver program: /SMB40/FM06P
GOODS RECEIPT
Output type         : WE01
ScriptForm Name     : WESCHEINVERS1
smartform name      : /SMB40/MMGR1_A
smartform driver program: /SMB40/M07DR
GOODS ISSUE
Output type         : WA01
ScriptForm Name     : WA_SCHEINVERS1
smartform name      : /SMB40/MMGI1_A
smartform driver program: /SMB40/M07DR
FI Forms
Account Statement   : F140_ACC_STAT_01
Cheque Printing     : F110_PRENUM_CHEK
Balance Confirmation: F130_confirm_01
Dunning Form:         F150_DUNN_01
check the link below it provides steps to convert sap scripts to smartforms
http://www.ficoexpertonline.com/downloads/Iyer_SmartForms.pdf
SMARTFORMS -Driver Program
PO: /SMB40/FM06P
SO: /SMB40/RVADOR01
GR: /SMB40/M07DR
with regards,
Hema Sundara.
pls give points if u find this helpful.

Sending Smart form to Printer in SRM

Hi All,
I am trying to send a smartform to Printer in SRM ITS. I gave output options and control parameters . When i see the Print dialog box i dont see the Front end printers in that. Normally when we pass LOCL we should see default printer in Print dialog.
When i do print, spool is creating but its not printing at local printer .
I am doing this in SRM ITS ... could you kindly any one tell me what steps need to take to print a smart form at local printer when we call form ?
Thanks

Hi
Please elaborat, when you need this SMARTFORM to get triggered.
By the way, Have you tried implementaing the following BADIs ?
BBP_CHANGE_SF_BID                                             Smartform for E-Mails to Bidder
BBP_CHANGE_SF_CTR                                             Change Smart Form for Contract Output
BBP_CHANGE_SF_ERS                                             Change Smart Form
BBP_CHANGE_SF_SC                                              Smart Form Shopping Cart Print
BBP_CHANGE_SF_VERS                                            Change Smart Form for Version Comparison
BBP_PROCESS_AUC                                               Process Smart Form with Changed Interface
BBP_PROCESS_BID                                               Process Smart Form with Changed Interface
BBP_PROCESS_CTR                                               Process Smart Form with Changed Interface
BBP_PROCESS_PO                                                Process Smart Form with Changed Interface
BBP_PROCESS_QUOT                                              Process Smart Form with Changed Interface
Hope this will help.
Please rewards suitable points.
Regards
- Atul

Smart forms background logo

Hi
Please clarify me regarding smart forms background logo. I'm trying to migrate sap script into smart forms, for the background logo in smart form is it required to write ABAP code, please let me know?
2) Is it possible for background pictures in script? Is there any document regarding logo/pictures in sap script or smartforms? is there standard forms like purchase order etc., in smart forms? Please correct me If i'm wrong...
Regards
sree reddy

Hi
Background LOGOS are possible only in smartforms not in Scripts
see the logo printing for Scripts and Smartforms and the important smartforms and scripts with their programs
               SAP SCRIPT
To create a logo in SAP printouts just do the following
1. Save a Logo using Imaging, Paint shop Pro or Corel Draw as Tiff file.
2. Run program RSTXLDMC and enter the following parameters
   Enter file name                     C:\COMPLOGO.TIF
   UOM                          CM
    Line width for text                132
    Text name                     ZHEX-MACRO-COMPLOGO
    Text ID                          ST
    Text language = E
    Number of Tiff gray levels (2,4,9) 2
3. Then Create a new window 'COMP' with attributes;
Window COMP description Company Logo
Left margin 7.00 CH window width 10.00 CH
Upper margin LN window height 8.00 LN
Finally in the text element, mention
        /: INCLUDE 'ZHEX-MACRO-COMPLOGO' OBJECT TEXT ID ST LANGUAGE 'E'.
Please note that if object name is not indicated as 'ZHEX... the logo may not be printed!
You will not be able to see the logo in a test print. The same will be printed in actual printout.
                      SMARTFORM
1)     In Smart Forms Editor, In left pane, right Click any Page (say Page1) and select Create -> Window, Give it a name and Description (Say Window1)
2) Right Click on Window (Window 1) and select Create -> Graphics, Give it a name and description
3) In general Attributes, Select Name, get search help (F4) , you will find a list of pictures
4) Select any picture and set its Resolution in DPI
5) Press F9 to open Smart Forms Builder, Select window (Window1) and In Output options window set, size and   position of the Logo
6) Set any other parameters if required, save and activate.
7) If there is only 1 Window in the forms, set it as Main Window in general attributes.
8) Use TCode SE78 to upload new pictures and logos.
look at Thread Dynamic Graph in smartforms
Refer the links also -
Re: Dinamic Graph in smartforms
How to get file perperties in Unix server
SD
SALES ORDER/ENQUIRY/QUOTATION
Output type         : BA00
ScriptForm Name     : RVORDER01
Driver Program Name : RVADOR01
smartform name
DELIVERY NOTE
Output type         : LD00
ScriptForm Name     : RVDELNOTE
Driver Program Name : RVADDN01
smartform name      : LE_SHP_DELNOTE
Smartform Driver Pgm: RLE_DELNOTE
INVOICE
Output type         : RD00
ScriptForm Name     : RVINVOICE01
Driver Program Name : RVADIN01
smartform name      : LB_BIL_INVOICE
Smartform Driver Pgm: RLB_INVOICE
MM
PUCHASE ORDER/RFQ/CONTRACT
Output type         : NEU
ScriptForm Name     : MEDRUCK
Driver Program Name : SAPMF06P
smartform name      : /SMB40/MMPO_L
smartform driver program: /SMB40/FM06P
GOODS RECEIPT
Output type         : WE01
ScriptForm Name     : WESCHEINVERS1
smartform name      : /SMB40/MMGR1_A
smartform driver program: /SMB40/M07DR
GOODS ISSUE
Output type         : WA01
ScriptForm Name     : WA_SCHEINVERS1
smartform name      : /SMB40/MMGI1_A
smartform driver program: /SMB40/M07DR
FI Forms
Account Statement   : F140_ACC_STAT_01
Cheque Printing     : F110_PRENUM_CHEK
Balance Confirmation: F130_confirm_01
Dunning Form:         F150_DUNN_01
check the link below it provides steps to convert sap scripts to smartforms
http://www.ficoexpertonline.com/downloads/Iyer_SmartForms.pdf
SMARTFORMS -Driver Program
PO: /SMB40/FM06P
SO: /SMB40/RVADOR01
GR: /SMB40/M07DR
Reward if useful
regards
Anji

Va32-standard print program, and smartform

Hi experts,
i need to find out the standard print program for va32 or va33. how to find out.
i have a smartform /SMB40/SDSDA_L,,,,,for this one which print program i can use. is this one correct for for va32, ifany change is there,,,u can suggest me.

Hi
check the NACE tcode or in TNAPR table by entering the output type field
You can use the driver program of SO: /SMB40/RVADOR01 of Sales order to Sch Agreement also, use this
script details for
SALES ORDER/ENQUIRY/QUOTATION/SCH AGREEMENT/CONTRACT
Output type : BA00
ScriptForm Name : RVORDER01
Driver Program Name : RVADOR01
Reward points for useful Answers
Regards
Anji

Form with logo

hii,
1. provide me a form with logo so tht i can test in IDES.
regards
rahul
Title was edited by:
        Alvaro Tejada Galindo

Hi
There are some Standard Sap Scripts in SAP. We cant directly execute them in scripts we have to use some T-codes and by giving some input to the required fields we can see the output printform.
I will show one example. There are some Standard Sap Scripts such as MEDRUCK which is a standard Sap Script for Purchase Order and RVINVOICE01 for billing and so on...
To see oupt of MEDRUCK go to T-code ME9F give purchase order number and execute select one number and click on dislplay messages button on application tool bar you can find the print form of MEDRUCK.
You cannot change the Standard Sap Scripts but you can use Standard Sap Scripts and Copy them to userdefined Script and can make changes to them and replace standard Sap Script with usedefind script.
Ex: Go to SE71,
on menu bar u find Utilities->copy from Client. click on it u ll find new screen showing
Form name:
Source Clinet:
Target Form:
give Form name as usedefined form name EX: ZFORM1
Source client as 000 and
Target form as MEDRUCK.
execute.
Now, the standard from MEDRUCK is copyied to your form ZFORM1.
NOW, go to SE71 and give form name as ZFORM1 and do some changes to the form such as adding logo any thing. save and Activate.
Now, you have done changes to the Form ZFORM1 and u have to replace your form with standard SAP Script.
Go to NACE Transaction.
on Applications select EF for purchase order and click Output types button on application tool bar.
now select NEU as output types dobule click on Processing Routines.
now click on Change option on application tool bar and on right side u find MEDRUCK in form place replace MEDRUCK with ZFORM1 and SAVE.
go back twice and now go to T-code ME9F give the purchase order number and execute and select one option and click on display messges button .
you will find the changes that you have done in ZFORM1. so we cant chage the standard Sap Scripts by copying the Standard Sap Scripts we can chage and replace with our forms.
SD
SALES ORDER/ENQUIRY/QUOTATION
Output type         : BA00
ScriptForm Name     : RVORDER01
Driver Program Name : RVADOR01
smartform name
DELIVERY NOTE
Output type         : LD00
ScriptForm Name     : RVDELNOTE
Driver Program Name : RVADDN01
smartform name      : LE_SHP_DELNOTE
Smartform Driver Pgm: RLE_DELNOTE
INVOICE
Output type         : RD00
ScriptForm Name     : RVINVOICE01
Driver Program Name : RVADIN01
smartform name      : LB_BIL_INVOICE
Smartform Driver Pgm: RLB_INVOICE
MM
PUCHASE ORDER/RFQ/CONTRACT
Output type         : NEU
ScriptForm Name     : MEDRUCK
Driver Program Name : SAPMF06P
smartform name      : /SMB40/MMPO_L
smartform driver program: /SMB40/FM06P
GOODS RECEIPT
Output type         : WE01
ScriptForm Name     : WESCHEINVERS1
smartform name      : /SMB40/MMGR1_A
smartform driver program: /SMB40/M07DR
GOODS ISSUE
Output type         : WA01
ScriptForm Name     : WA_SCHEINVERS1
smartform name      : /SMB40/MMGI1_A
smartform driver program: /SMB40/M07DR
FI Forms
Account Statement   : F140_ACC_STAT_01
Cheque Printing     : F110_PRENUM_CHEK
Balance Confirmation: F130_confirm_01
Dunning Form:         F150_DUNN_01
check the link below it provides steps to convert sap scripts to smartforms
http://www.ficoexpertonline.com/downloads/Iyer_SmartForms.pdf
SMARTFORMS -Driver Program
PO: /SMB40/FM06P
SO: /SMB40/RVADOR01
GR: /SMB40/M07DR
Regards
Anji

Strange error message duting Creation bid invitation

hi!
i try to create Bid invitation and add Bidder with contact person
and get strange error message
Message not found (in main memory)
Do you know what's a problem?
Thanks.

Hi
Which System version are using ?
Please go through the following SAP OSS Notes ->
Note 1037262 BBP_QUOT_BOB: Surrogate Bid receives Message not found error
Note 787154 Unreasonable error message in contract output forecast
Note 732472 Incomplete attributes of a user lead to termination
Note 684024 Error "Message not found (in main memory)"
Note 641960 New processing of terms of payment in EBP 3.5
Note 502534 Message "Log not found (in main memory)" in CW
Hope this will definitely help.
Regards
- Atul

Nudge fields in forms

Acrobat 9 pro.
I'm trying to add rows and columns of checkboxes to an existing form from a client. They need to line up inside the existing lines on the form. I figured out how to use "place multiple fields" to give me what i need sort of. I can use the "change width" and "change height" settings in the "place multiple fields" window to spread them out to fit sort of but it's not accurate enough. The width isn't a problem but the height is. As I increment the height, they don't spread out for every size I choose. For example if I click the spin button 5 times, the height only changes once. It's as if it only accepts certain increments. I've also tried moving them manually with the arrow keys (nudge) after placing the fields but that's not accurate either. One nudge is TOO big and I can't find anything in the settings to allow me to change the nudge size. I sure hope there's a way to get this done accurately! I've tried changing my grid settings as well. Didn't do anything.

Hi
See the following scripts/smartforms and their driver programs
You can see the each form in SE71 and go to the windows(MAIN) and see the fields used
SD
SALES ORDER/ENQUIRY/QUOTATION
Output type         : BA00
ScriptForm Name     : RVORDER01
Driver Program Name : RVADOR01
smartform name
DELIVERY NOTE
Output type         : LD00
ScriptForm Name     : RVDELNOTE
Driver Program Name : RVADDN01
smartform name      : LE_SHP_DELNOTE
Smartform Driver Pgm: RLE_DELNOTE
INVOICE
Output type         : RD00
ScriptForm Name     : RVINVOICE01
Driver Program Name : RVADIN01
smartform name      : LB_BIL_INVOICE
Smartform Driver Pgm: RLB_INVOICE
MM
PUCHASE ORDER/RFQ/CONTRACT
Output type         : NEU
ScriptForm Name     : MEDRUCK
Driver Program Name : SAPMF06P
smartform name      : /SMB40/MMPO_L
smartform driver program: /SMB40/FM06P
GOODS RECEIPT
Output type         : WE01
ScriptForm Name     : WESCHEINVERS1
smartform name      : /SMB40/MMGR1_A
smartform driver program: /SMB40/M07DR
GOODS ISSUE
Output type         : WA01
ScriptForm Name     : WA_SCHEINVERS1
smartform name      : /SMB40/MMGI1_A
smartform driver program: /SMB40/M07DR
FI Forms
Account Statement   : F140_ACC_STAT_01
Cheque Printing     : F110_PRENUM_CHEK
Balance Confirmation: F130_confirm_01
Dunning Form:         F150_DUNN_01
check the link below it provides steps to convert sap scripts to smartforms
http://www.ficoexpertonline.com/downloads/Iyer_SmartForms.pdf
SMARTFORMS -Driver Program
PO: /SMB40/FM06P
SO: /SMB40/RVADOR01
GR: /SMB40/M07DR
You can use the TNAPR Table or NACE transaction to find the respective Script/form for the corresponding transaction
Regards
Anji

Contract Output

Similar Messages

Maybe you are looking for