Layout misallignment in SAPScript
Hi,
I have written a print program for sapscript and designed a layout for it.
Three fields have been defined in the layout set.
Every time the loop runs around write_form the three field gets printed.
<b>Print program logic:</b>
loop at iresb. "IRESB is internal table.
IF IRESB-SHKZG = 'S'.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'CO-PRO' "Text Element
WINDOW = 'MAIN'.
ENDIF.
endloop.
<b>Layout logic:</b>
/E CO-PRO
A1 &IRESB-MATNR&,, ,,&IRESB-MAKTX&,, ,,&IRESB-BDMNG&
<b>Now the problem is I get output as follows:</b>
MACHINE1 CUTTING 5.000
M2 DRILLING 2.000
BIGMACHINE FITTING 7.000
<b>But I want output like:</b>
Machine1 Cutting 5.000
M2 DRILLING 2.000
BIGMACHINE FITTING 7.000
(If I keep the tab position constant then if the description of next matnr is long or short as compared to previous one the other data gets mis-alligned as you can see from the above one which I am getting)
What is solution for this ?
Tushar,
In your Paragraph Format 'A1' you want to assign the "Tabs". This option allows you to define the tab spacing. When you write out the text, the ",," says to use the next Tab.
Try definign the tabs as follows:
1 11CH Left
2 33CH Left
Then change the code in your SAPscript to be as follows:
A1 &IRESB-MATNR(10)&,,&IRESB-MAKTX(20)&,,&IRESB-BDMNG&
This will be he equililent to:
write:/ iresb-matnr(10).
write at 11 iresb-maktx(20).
write at 33 iresb-bdmng.
Let me know if you need more info.
Cheers,
Pat.
Similar Messages
-
Invoice Layout configuration for a specific customer within a sales org.
Hi,
I have a situation where the invoice layout need to be configured for one particular customer within a sales org in a different style from rest of the customers.
Could someone let me know how to do it please.
Thanks.
Best regards,
SrikrishhnaBy u201Cinvoice layoutu201D, I assume you mean layout of the print output. If so, then
u2022 Set up a new output type as a copy of your standard output type. Assign an access sequence containing customer.
u2022 Add the new type to your active output determination procedure and assign an appropriate requirements routine (if any).
u2022 Assign a layout set (smartform, sapscript, adobe, etc.) that meets your customeru2019s requirements.
u2022 Maintain the condition record.
And away you go.
Regards,
zKen -
what r all the necessary tcodes in sapscripts including monitoring tcodes if avl
Hi,
Take this freq. used t codes....I think it wil be very usefull for u.
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE12 ABAP/4 Dictionary Display
SE13 Maintain Technical Settings (Tables)
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser
SE17 General Table Display
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP/4 Program Development
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE51 Screen Painter
SE80 ABAP/4 Development Workbench
SE71 SAPscript layout set
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE91 Maintain Messages
SE93 Maintain Transaction Codes
If its going to be helpfull reward points.
Sakthi. -
Payment program (RFFOAU_T)
Hi,
Can any one please let me know the functionality of payment program and use of this program.
Thanks in advance.Short text
Payment Medium for Australia - Bank Transfers/Debit Memo BECS
Description
The program issues data medium exchange in BECS, the disk format used by Australian banks.
As well as the payment media, the accompanying payment advice notes, data medium accompanying sheets and payment summaries can also be printed in one program run.
Requirements
Payment Program Configuration
The parameters that control the way in which the payment medium programs function are configured in Customizing. For more information on configuring the payment program, refer to the Implementation Guide.
Configure payment program
1. Here you need to make specifications for the paying company code. To do this, select the relevant paying company code by choosing Paying Company Codes ->.
If payment advices are to be printed, define a SAPscript payment advice form for use with all company code payment methods. You will find the form F110_IN_AVIS as an example in the standard system.
You need to create and enter text modules in which the texts for the header, footer, signature and sender are stored. These modules can be included in the forms when they are used. To do this, choose Sender Details, from where you can also branch into text maintenance by selecting the modules. The names of the text can be defined by the user, for example F_0001_HEADER for the letter header in company code 0001.
Proceed
2. Here you need to allocate the name of the payment medium program RFFOAU_T to the payment method to avoid incorrect payment media being issued with another program by mistake.
To do this, first choose Payment methods in country, then select the country of your paying company code and the payment method you require, and then maintain the data necessary for printing the form.
Proceed
3. Here you need to make company code specifications for the payment method. To do this, choose Payment Methods In Company Code, then select the paying company code and the payment method. In this menu maintain the following data by choosing Form data or Payment Advice Control:
The SAPscript form for accompanying sheets (F110_AU_BECS in the standard system) as the next form (for DME).
The issuer data.
Sorting the correspondence.
Sorting the line items.
Proceed
Note: You should fill out the issuer specifications as follows:
Line 1 Issuer's name (26 characters long)
Line 4 Issuer's city
4. You need to make further specifications for creating the payment medium in Customizing of the house banks. Select the relevant paying company code by choosing House Banks. In the maintenance of the house banks select your house bank and then maintain the required data via the button Data Medium Exchange. For more details refer to the online documentation for the relevant fields.
Proceed
Notes:
a) Common BSB numbers, which give a bank a unique identification, must be maintained for Australian banks. This three-character abbreviation is defined in the publication 'BSB Numbers in Australia', and is entered in the SAP system as part of the DME data maintenance in the field Altern. bank ID.
b) You need to maintain the lead days. The processing date (batch due date) is calculated from the posting date plus the lead days.
c) The company number (user identification number) is also transferred from the house bank's DME data.
Setting up and changing the SAPscript forms (layout sets)
The following describes the layout of the SAPscript forms in brief. If the forms available in the standard system are sufficient for your requirements, you can skip this part of the documentation.
You can find further information on forms and the SAPscript editor in the guides on styles and form maintenance and word-processing in the SAPscript editor: Select the menu path Help -> SAP Library.
1. When setting up SAPscript forms (layout sets), symbols are included in the text; these are then replaced by actual values when the payment medium programs are run. The fields which can be used for this are defined in the Repository and contained in the following structures:
REGUH Settlement data from the payment program
REGUP Edited invoice items from the payment program
REGUD Formatted data for printing the forms
SPELL Amounts and digits in words.
FSABE Data on accounting clerk.
2. If you want the document long text for an accounting invoice document to be printed on the payment advice form, you must make the following enhancement in element "Long text for invoice document" (specially designed for this purpose):
/: DEFINE &TXT& := '®UP-BUKRS()&®UP-BELNR(RF0)&®UP-GJAHR&'
/: INCLUDE &TXT& OBJECT BELEG ID xyz
The text ID that you must enter for this text (xyz) is defined in the configuration menu and can be read from there. In the standard system, text ID 0003 is predefined for the payment advice information.
Proceed
3. Layout of the payment advice form (F110_IN_AVIS in the standard system)
Pages
FIRST First page per payment advice
NEXT Subsequent pages if page overflow
EDI List of payment advice notes sent per EDI
LAST Form summary section per house bank
Windows and elements
HEADER Letter header
ADDRESS Sender and address of the payee
PAGE Page counter
INFODate, payment document number, etc.
INFO 605Account number of the sender at the recipient
INFO2 Information on the next pages
REPEAT Information for the test print or proposal run
MAIN Form of address before the letter
MAIN 610-x Short text for payment method x
MAIN 610 Letter when 610-x is missing
MAIN 612Alternative payee
MAIN 613 Notification takes place in order
MAIN 614 Signature
MAIN 615 Heading of the invoice item information
MAIN 620 Carryforward at page top after page overflow
MAIN 625Invoice item information
MAIN 625-TXLong text for invoice
MAIN 625-HRInformation line for Payroll Accounting
MAIN 630Sum total
MAIN 631 User-defined text after invoice items
MAIN 675 Header for EDI advices
MAIN 676List of EDI advices
TOTAL 630 Sum total of fixed items
CARRYFWD 635 Carryforward at page bottom for page overflow
FOOTER Letter footer
SUMMARY Form summary section
4. Layout of the data medium accompanying sheet (F110_AU_BECS in the standard system)
Pages
DME Accompanying sheet
LAST Form summary section for each house bank
Windows and elements
DOMESTIC 535 Accompanying sheet
Check that the SAPscript forms (layout sets) which you use have the layout described and, in addition, check that the forms are active (both in the original language as well as in all languages into which the forms were translated).
Proceed
Periodic processing
Before the payment medium programs can be started, the payment program run must have been successfully completed. Check the status of the payment run, or schedule the payment medium programs by specifying one or more variants.
Proceed
Note: If you want to use th 'Payment document update' option, the payment documents must be updated between the time of the payment program run and the time of the payment medium program run.
Output
Forms and lists
Printout files are created per company code and house bank. These can either be printed via the print manager or immediately. Depending on the parameter you select, you can print out one or more of the following:
Accompanying sheet for the payment medium
Payment advice notes (if the information cannot be sent via EDI)
Payment summary
Error log
The number of output files is specified in the flow trace; this makes finding and allocating them within the print manager easier.
Proceed
Note: If the program was started online, then you reach the print manager from the list by selecting one of the output files displayed.
Payment Advice Notes
In addition to being able to print payment advice notes, you can also send these via EDI, fax or email.
1. To send a business partner a payment advice note via EDI, you need to select the indicator Payment advice note per EDI and maintain the partner agreement on screen "Payment Transactions Accounting" in the master record.
Proceed
Using an external converter, the IDoc created by the program can be converted into the EDI format you require (REMADV for example) and then sent.
2. To send a business partner a payment advice note by fax or email, you must use the process interface 00002040 (Business Transaction Events) to define the selection of the message type (printout, fax or email). Before you can do this, however, you must have carried out the necessary technical (Basis) settings for faxing or sending emails.
Process interface 00002050 can also be used to change or configure the print parameters and the parameters for optical archiving for payment advice notes.
DME
Data medium exchange in this case involves the creation of a file which corresponds to the rules of the credit institution in question for automatic payment transactions and which contains all the necessary payment information.
The information relevant for the payment medium (file format, creation data, payment amount in local currency, payment documents involved etc.) are stored in the system and can be called up via the DME manager.
Other functions of the DME manager are:
Downloading the file into your local (PC) file system
Displaying and printing the file contents
Generating a payment summary for the data medium
Proceed
You will find further information about the structure of the data medium in the technical description.
Output in the file system
If required, the file can be written into the file system. The file created can be copied onto a PC via the DME manager. When doing this, you should search for files by download since the data medium is not managed within the SAP System but has already been stored in the file system by means of the payment medium program.
Proceed
If the file name is not to be specified by parameter, then it is generated by the program. It then consists of the disk format, date and time of creation as well as a consecutive number so that the file name in the file system is unique.
If the file name is specified by the user, then a consecutive number is likewise added for each program run. From an organizational point of view, however, you should make sure that already existing files are not overwritten.
Note: If you cannot find the file via the DME manager, then this can be due to the following reason: the directory which was written to when the payment medium program was started (for example, in background processing), cannot be read online. Therefore you should choose a directory which can be written to and read by different machines.
Due to the above-mentioned problems and the affect this has an data security, it is advisable not to write data to the file system. It may be advisable to use this method in cases where the data medium file is 'picked up' from the file system by an external program to be passed on to the bank.
Output in the TemSe
If required, the file created can be stored within the SAP System (stored in the TemSe and not in the file system), thus protecting it from unauthorized external access. You can download the file into the user's file system via DME management.
The name of the file to be created during the download can be determined when running the payment medium program; the contents of the file name parameter are stored in the management data and defaulted when running the download.
Proceed
User exit
You can modify the dataset for data medium exchange by using the user exit interface defined. You can, however, only change the fields of the DTAMAU0 structure.
Creating a user exit
The print program calls up the EXIT_RFFOEXIT_210 function module. Please take the input and output parameters for the user exit from the function module interface.
Proceed
Create an include file with the name ZXFORU32 to program the modifications required.
Proceed
The file is included in the EXIT_RFFOEXIT_210 function module. Use the Enhancements transaction for activating or deactivating your user exits by activating or deactivating the RFFOX210 project affected.
Proceed
Error messages and error log
Termination of processing
You can find out the reason why processing was terminated (for example, production run not yet carried out, form does not exist or is not active) by looking at the error message or the related long text.
Internal SAPscript error
Check the layout of the forms. It must fulfil the above-mentioned conditions. You cannot, for example, create a bank transfer with the check print program, since bank transfers and checks have a completely different layout structure.
Error log
If errors which do not terminate the payment medium program occur when creating the output, the system lists them in the error log. If such a log is created, you must look it over because only you can decide whether the payment medium or payment advices are useless due to the errors the system finds, and decide whether they must be recreated after the errors have been rectified.
During background processing, the system outputs the error log twice, in the flow trace for the job and in a printout file. The flow trace contains information on how to rectify the errors (from the error message long texts).
You can display the long text online by choosing the error log from the list of generated output files and then the error message in question.
plz reward points if dis helps -
Hi Gurus,
Send me a list of Tcodes in SAP.
Thanks in Advance,
SakthiPlant Maintenance (PM)
Stephan Nilsson was kind enough to share some PM transactions. Stephan Nilsson was kind enough to share some PM transactions.
IW31 Create Plant Maintenance Order
IW32 Change Plant Maintenance Order
IW33 Display Plant Maintenance Order
IW34 Create Notification Order
IW51 Create Service Notification
IW52 Change Service Notification
IW53 Display Service Notification
IW54 Create Service Notification :Problem notification
IW55 Create Service Notification :Activity Request
IW56 Create Service Notification :Service Request
IW57 Assign deletion Flag to Completed Service Notifications
IW58 Change Service Notifications: Selection of Notification
IW59 Display Service Notifications: Selection of Notification
Production Planning
Tymon Kerste has provided me with these PP tcodes. Tymon Kerste has provided me with these PP tcodes.
C001 Create Production Order
C005N Collective Release
C011N Time Ticket
C012 Confirmation - Collective
C013 Confirmation - Cancel
C00IS Production order information system
C0GI Reprocess Goods Movements
C223 Maintain production version
General Notes
You can execute the following commands in the transaction code (tcode) field with Enter. You will find some useful transaction codes below to work in tandem with the following commands:
To call a transaction - In the same session (window) Enter: /nxxxx (xxxx = transaction code). - In an additional session, Enter: /oxxxx (xxxx = transaction code).
If you enter this function before any of the tcodes below, you are able to break out of your current screen/business and begin a completely new session. Otherwise, the current business process has to be terminated, and return to the initial user screen (the main menu) has to be initiated before entering tcode spro). /o tcode saves you the effort of having to do this.
To end the current transaction Enter: /n. Caution: Unsaved changes are lost without warning
To delete the current session. Enter: /i.
To generate a session list Enter: /o.
To log off from the system Enter: /nend.
From John O'Meara
OSS Note 0026171 has additional information on OKCodes in SAP, and is a very useful read
BASIS/ABAP
USMM Pressing F8 will display all hotpacks applied.
SEARCH_SAP_MENU Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
DI02 ABAP/4 Repository Information System: Tables.
LSMW Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.
OSS1 SAP Online Service System
OY19 Compare Tables
SM13 Update monitor. Will show update tasks status. Very useful to determine why an update failed.
S001 ABAP Development Workbench
S001 ABAP/4 Development Weorkbench. (from [email protected])
S002 System Administration. (from [email protected])
SA38 Execute a program. (from [email protected])
SCAT Computer Aided Test Tool
SCU0 Compare Tables
SE01 Old Transport & Corrections screen
SE03 Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09 Workbench Organizer
SE10 New Transport & Correction screen
SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12 Dictionary: Initial Screen - enter object name. (from [email protected])
SE13 Access tables in ABAP/4 Dictionary. (from [email protected])
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser: Initial Screen. (from [email protected])
SE16N Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.
SE17 General Table Display
SE24 Class Builder
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE48 Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.
SE49 Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.
SE51 Screen Painter: Initial Screen. (from [email protected])
SE54 Generate View Maintenance Module
SE61 R/3 Documentation
SE62 Industry utilities
SE63 Translation
SE64 Terminology
SE65 R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68 Translation Administration
SE71 SAPscript layout set
SE71 SAPScript Layouts Create/Change
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE83 Reuse Library. Provided by Smiho Mathew.
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Dictionary Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE91 Maintain Messages
SE92 Maintain system log messages
SE93 Maintain Transaction. (from [email protected])
SEARCH_SAP_MENU From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SEU Object Browser
SHD0 Transaction variant maintenance
SM04 Overview of Users (cancel/delete sessions)
SM12 Lock table entries (unlock locked tables)
SM21 View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30 Maintain Table Views. (from [email protected])
SM31 Table Maintenance
SM32 Table maintenance
SM35 View Batch Input Sessions
SM37 View background jobs
SM50 Process Overview. (from [email protected])
SM51 Delete jobs from system (BDC)
SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN Display the menu path to get to a transaction
SMOD/CMOD Transactions for processing/editing/activating new customer enhancements.
SNRO Object browser for number range maintenance. (from [email protected])
SPRO Start SAP IMG (Implementation Guide). (from [email protected])
SQ00 ABAP/4 Query: Start Queries
SQ01 ABAP/4 Query: Maintain Queries
SQ02 ABAP/4 Query: Maintain Funct. Areas
SQ03 ABAP/4 Query: Maintain User Groups
SQ07 ABAP/4 Query: Language Comparison
ST05 Trace SQL Database Requests. (from [email protected])
ST22 ABAP Dump analysis
SU53 Display Authorization Values for User. (from [email protected])
WEDI EDI Menu. IDOC and EDI base.
WE02 Display an IDOC
WE07 IDOC Statistics
Human Resources
PA03 Change Payroll control record
PA20 Display PA Infotypes
PA30 Create/Change PA Infotypes
PP02 Quick Entry for PD object creation
PU00 Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.
Sales and Distribution (SD)
OLSD Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data
VA01 Create Sales/Returns Order:Initial Screen
VB21 Transaction for Volume Lease Purchases (done as a sales deal)
VK15 Transaction used to enter multiple sales conditions (most will be entered here)
SAP Office
SO00 send a note through SAP, can be sent to internet, X400, etc
FI Financial Management
FGRP Report Writer screen
FM12 View blocked documents by user
FST2 Insert language specific name for G/L account. (from [email protected])
FST3 Display G/L account name. (from [email protected])
KEA0 Maintain operating concern. (from [email protected])
KEKE Activate CO-PA. (from [email protected])
KEKK Assign operating concern. (from [email protected])
KL04 Delete activity type. (from [email protected])
KS04 Delete a cost centre. (from [email protected])
KSH2 Change cost centre group - delete. (from [email protected])
OBR2 Deletion program for customers, vendors, G/L accounts. (from [email protected])
OKC5 Cost element/cost element group deletion. (from [email protected])
OKE1 Delete transaction data. (from [email protected])
OKE2 Delete a profit centre. (from [email protected])
OKI1 Determine Activity Number: Activity Types (Assignment of material number/service to activity type) (from [email protected])
OMZ1 Definition of partner roles. (from [email protected])
OMZ2 Language dependent key reassignment for partner roles. (from [email protected])
Material Management (MM)
MM06 Flag material for deletion. (from [email protected])
OLMS- materials management configuration menu, most of the stuff under this menu is not under the implementation guide
MM configuration transactions
OLMB- Inventory management/Physical Inventory
OLMD- MM Consumption-Based Planning
OLME- MM Purchasing
OLML- Warehouse Management
OLMR- Invoice Verification
OLMS Material Master data
OLMW- MM Valuation/Account Assignment
Config Related
OLE OLE demo transaction
OLI0 C Plant Maintenance Master Data
OLI1 Set Up INVCO for Material Movements
OLI8 Set Up SIS for Deliveries
OLIA C Maintenance Processing
OLIP C Plant Maintenance Planning
OLIQ New set-up of QM info system
OLIX Set Up Copying/Deleting of Versions
OLIY Set Up Deletion of SIS/Inter.Storage
OLIZ Stat Set Up INVCO: Invoice Verif
OLM2 Customizing: Volume-Based Rebates
OLMB C RM-MAT Inventory Management Menu
OLMD C RM-MAT MRP Menu
OLME C MM Menu: Purchasing
OLML C MM Menu for Warehouse Management
OLMR C RM-MAT Menu: Invoice Verification
OLMS C RM-MAT Master Data Menu
OLMW C RM-MAT Valuation/Acct. Assgt. Menu
OLPA SOP Configuration
OLPE Sales order value
OLPK Customizing for capacity planning
OLPR Project System Options
OLPS Customizing Basic Data
OLPV Customizing: Std. Value Calculation
OLQB C QM QM in Procurement
OLQI Analysis
OLQM Customizing QM Quality Notifications
OLQS C QM Menu Basic Data
OLQW C QM Inspection Management
OLQZ Quality Certificates
OLS1 Customizing for Rebates
OLSD Customizing: SD
OLVA C SD Sales Menu
OLVD C SD Shipping Menu
OLVF C SD Billing Menu
OLVS C SD Menu for Master Data
SPRO Start SAP IMG (Implementation Guide). (from [email protected])
reward points if useful.
thanks,
usha -
Explain flow of standard cheque print program
Hi All,
Can anybody explain the flow of standard cheque print program RFFOUS_C.
The standard cheque print program will use Z form layout to print cheque and remittance advice.I have to add few form routines for RFFOUS_C. Also explain the functions of below mentioned form routines.
Form routines:
FM_CHQ_AMT
Move protective u201C*u201D from field REGUD-SWNES and load value into AMOUNT_CHEQUE.
FM_REMOVE_STAR
Move protective u201C*u201D from field REGUD-SWNES and load value into AMOUNT_FIXED.
Append the currency to the end of the value in AMOUNT_FIXED (if Currency = ZAR u2013 append the value R)
FM_CHQ_AMT_WORDS
u2022 Remove extra spaces from the amount in words
u2022 If currency = ZAR insert the word RANDS after the Rands amount else insert the value in field REGUD-WAERS
u2022 Combine Rands value and the cents value with the text -AND- (i.e. Rands value u2013AND- cents value)
u2022 End the cents value with the text CENTS
u2022 End the amount in words with the text u201C-ONLYu201D.
u2022 If the amount text is longer than 52 characters split the text into two lines (line 1 (AMOUNT_WORD_1) may hold 52 characters and line 2 (AMOUNT_WORD_2) may hold 62 characters u2013 maximum capacity for writing cheques).
u2022 Overlay any spaces with the character u201C|u201DInternational Payment Medium - Check (with check management)
Description
This program prints prenumbered check forms or non-prenumbered checks whose number is to be assigned from a predefined number range, and links the check number to SAP payment document number or the check number to the settlement result.
In addition to the checks, you can print their payment advice notes and payment summaries in one program run.
Requirements
Check lots
The checks which are ready for printing are divided up into lots. The user can freely define the criteria by which lots are formed (for example, location of check storage, accounting clerk or printer). The check numbers of a lot must be consecutive.
A lot is assigned to the checks to be printed via a parameter whose number you define via the corresponding check lot management in the system.
After entering the lot number, the print program independently searches for the first free check number (even if this is in the next lot rather than in the lot specified).
Payment Program Configuration
The parameters that control the way in which the payment medium programs function are configured in Customizing. For more information on configuring the payment program, refer to the Implementation Guide.
1. Here you need to make specifications for the paying company code. To do this, select the relevant paying company code by choosing Paying Company Codes ->.
If payment advices are to be printed, define a SAPscript payment advice form for use with all company code payment methods. You will find the form F110_D_AVIS as an example in the standard system.
You need to create and enter text modules in which the texts for the header, footer, signature and sender are stored. These modules can be included in the forms when they are used. To do this, choose Sender Details, from where you can also branch into text maintenance by selecting the modules. The names of the text can be defined by the user, for example F_0001_HEADER for the letter header in company code 0001.
2. Here you need to allocate the name of the payment medium program RFFOUS_C to the payment method to avoid incorrect payment media being issued with another program by mistake.
Furthermore, you can enter a short name (or 'print dataset', for example LIST1S) which makes it easier to find the generated forms in the print manager.
To do this, first choose Payment methods in country, then select the country of your paying company code and the payment method you require, and then maintain the data necessary for printing the form.
3. Here you need to make company code specifications for the payment method. To do this, choose Payment Methods In Company Code, then select the paying company code and the payment method. In this menu maintain the following data by choosing Form data or Payment Advice Control:
The SAPscript form for payment media (F110_PRENUM_CHCK in the standard system).
The issuer data.
Sorting the correspondence.
Sorting the line items.
The number of note to payee lines on the form and the payment advice note output in accordance with the specified number of lines
If you specify as many as required note to payee lines on the form then Payment Advice Output According to Number of Lines controls whether in addition a payment advice is always created or not.
Note: The issuer details are used on the payment medium for city and signature in the standard system:
Line 1 Name 1 of issuer
Line 2 Name 2 of issuer
Line 3 Blank
Line 4 City.
Setting up and changing the SAPscript forms (layout sets)
The following describes the layout of the SAPscript forms in brief. If the forms available in the standard system are sufficient for your requirements, you can skip this part of the documentation.
You can find further information on forms and the SAPscript editor in the guides on styles and form maintenance and word-processing in the SAPscript editor: Select the menu path Help -> SAP Library.
1. When setting up SAPscript forms (layout sets), symbols are included in the text; these are then replaced by actual values when the payment medium programs are run. The fields which can be used for this are defined in the Repository and contained in the following structures:
REGUH Settlement data from the payment program
REGUP Edited invoice items from the payment program
REGUD Formatted data for printing the forms
SPELL Amounts and digits in words.
FSABE Data on accounting clerk.
Note that check forms can be issued in foreign currency only if the currency key is also printed on them. If forms are only to be filled out for local currency checks (on which no space is defined for the currency key) then you should remove the symbol for the currency key ®UD-WAERS& from the check window. The program then prevents you from printing foreign currency checks.
2. If you want the document long text for an accounting invoice document to be printed on the payment advice form, you must make the following enhancement in element "Long text for invoice document" (specially designed for this purpose):
/: DEFINE &TXT& := '®UP-BUKRS()&®UP-BELNR(RF0)&®UP-GJAHR&'
/: INCLUDE &TXT& OBJECT BELEG ID xyz
The text ID that you must enter for this text (xyz) is defined in the configuration menu and can be read from there. In the standard system, text ID 0003 is predefined for the payment advice information.
Periodic processing
Before the payment medium programs can be started, the payment program run must have been successfully completed. Check the status of the payment run, or schedule the payment medium programs by specifying one or more variants.
Note: If you want to use th 'Payment document update' option, the payment documents must be updated between the time of the payment program run and the time of the payment medium program run.
Output
Forms and lists
Printout files are created per company code and house bank. These can either be printed via the print manager or immediately. Depending on the parameter you select, you can print out one or more of the following:
Payment medium
Payment advice notes (if the information cannot be sent via EDI)
Payment summary
Error log
The number of output files is specified in the flow trace; this makes finding and allocating them within the print manager easier.
Note: If the program was started online, then you reach the print manager from the list by selecting one of the output files displayed.
Payment Advice Notes
In addition to being able to print payment advice notes, you can also send these via EDI, fax or email.
1. To send a business partner a payment advice note via EDI, you need to select the indicator Payment advice note per EDI and maintain the partner agreement on screen "Payment Transactions Accounting" in the master record.
Using an external converter, the IDoc created by the program can be converted into the EDI format you require (REMADV for example) and then sent.
2. To send a business partner a payment advice note by fax or email, you must use the process interface 00002040 (Business Transaction Events) to define the selection of the message type (printout, fax or email). Before you can do this, however, you must have carried out the necessary technical (Basis) settings for faxing or sending emails.
Process interface 00002050 can also be used to change or configure the print parameters and the parameters for optical archiving for payment advice notes.
Check management
You can access information about the issued checks via check management, line item display for sub-ledger or bank accounts, or invoice and payment document display. A check register list can also be created for the respective payment run. Errors occurring during check number and document number allocation can also be rectified using check management. You can find check management within Accounts Receivable or Accounts Payable, both parts of Financial Accounting, as well as under the "Environment" menu option in the payment program.
For more information on check management, esp. about detailed solutions to possible error situations, refer to the FI Accounts Payable manual under Help->R/3 Library.
Error messages and error log
Termination of processing
You can find out the reason why processing was terminated (for example, production run not yet carried out, form does not exist or is not active) by looking at the error message or the related long text.
Internal SAPscript error
Check the layout of the forms. It must fulfil the above-mentioned conditions. You cannot, for example, create a bank transfer with the check print program, since bank transfers and checks have a completely different layout structure.
Error log
If errors which do not terminate the payment medium program occur when creating the output, the system lists them in the error log. If such a log is created, you must look it over because only you can decide whether the payment medium or payment advices are useless due to the errors the system finds, and decide whether they must be recreated after the errors have been rectified.
During background processing, the system outputs the error log twice, in the flow trace for the job and in a printout file. The flow trace contains information on how to rectify the errors (from the error message long texts).
You can display the long text online by choosing the error log from the list of generated output files and then the error message in question.
Close the thread once your question is answered.
Rgds,
SaiRam -
Hi
Give me the T code for the following. Need to extract the below information from the system which is related to MM.
"Z" Reports
Includes
Module pools
BDCs
Exits Function exits
Table exits
SD User exits
Menu exits
Scren exits
Field exits
WorkFlows Standard Rules
Standard tasks
Workflow templates
SapScripts Layout sets
Styles
Classes
ALEs ALE message types
IDOC Types
IDOC extensions
Functions Function group
Function Module
Data Dictionary Domains
Data Elements
Transparent Tables
Structures (Plain)
Structures (Append)
Pool tables
Secondary Index
Match code objects
Type groups
BADIs Implementations
Definitions
Vijay
Edited by: Vijay on Apr 6, 2009 3:14 PMHi,
If You want find Z reports go to SE38 and give Z* and F4,it will list all Z reports.
Please find the list of tcodes
SE01 Old Transport & Corrections screen
SE03 Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09 Workbench Organizer
SE10 New Transport & Correction screen
SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12 Dictionary: Initial Screen - enter object name.
SE13 Access tables in ABAP/4 Dictionary.
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser: Initial Screen.
SE16N Table Browser (the N stands for New, it replaces SE16).
SE17 General Table Display
SE24 Class Builder
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE48 Show program call hierarchy. Very useful to see the overall structure of a program.
SE49 Table manipulation. Show what tables are behind a transaction code.
SE51 Screen Painter: Initial Screen.
SE54 Generate View Maintenance Module
SE61 R/3 Documentation
SE62 Industry utilities
SE63 Translation
SE64 Terminology
SE65 R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68 Translation Administration
SE71 SAPscript layout set
SE71 SAPScript Layouts Create/Change
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE83 Reuse Library.
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Dictionary Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE91 Maintain Messages
SE92 Maintain system log messages
SE93 Maintain Transaction.
SEARCH_SAP_MENU From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SM30 Maintain Table Views.
SM31 Table Maintenance
SM32 Table maintenance
SM35 View Batch Input Sessions
SM37 View background jobs
SM50 Process Overview.
SM51 Delete jobs from system (BDC)
SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN Display the menu path to get to a transaction
SMOD/CMOD Transactions for processing/editing/activating new customer enhancements.
SNRO Object browser for number range maintenance.
SPRO Start SAP IMG (Implementation Guide).
SQ00 ABAP/4 Query: Start Queries
SQ01 ABAP/4 Query: Maintain Queries
SQ02 ABAP/4 Query: Maintain Funct. Areas
SQ03 ABAP/4 Query: Maintain User Groups
SQ07 ABAP/4 Query: Language Comparison
ST05 Trace SQL Database Requests.
ST22 ABAP Dump analysis
SU53 Display Authorization Values for User. -
Hi, all transactions codes are saved in which table?some transaction codes?
hi,
all transactions codes are saved in which table?i want some transaction codes?All transaction codes are stored in table TSTC. Their texts are displayed in TSTCT.
Here are some T-CODE's..
OSS1 SAP Online Service System
OY19 Compare Tables
S001 ABAP Development Workbench
S002 System Administration.
SA38 Execute a program.
SCAT Computer Aided Test Tool
SCU0 Compare Tables
SE01 Old Transport & Corrections screen
SE09 Workbench Organizer
SE10 Customizing Organizer
SE10 Customizing organizer requests for user (To release for transport enter user name, press Enter. Select changed object and select ReleaseSE10 New Transport & Correction screen
SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE11 ABAP/4 Dictionary.
SE12 Dictionary: Initial Screen enter object name
SE13 Access tables in ABAP/4 Dictionary.
SE14 ABAP/4 Dictionary: Database Utility.
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE15 ABAP/4 Repository Information System.
SE16 Data Browser
SE16 Data Browser: Initial Screen.
SE16 Display table contents
SE17 General Table Display
SE30 ABAP/4 Runtime Analysis
SE30 ABAP/4 Runtime Analysis: Initial Screen.
SE30 Run Time Analysis (press Tips and Tricks button for good stuff)
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Library.
SE37 ABAP/4 Function Modules
SE38 ABAP Editor
SE38 ABAP/4 Editor.
SE38 ABAP/4 Program Development
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE51 Screen Painter
SE51 Screen Painter: Initial Screen.
SE54 Generate View Maintenance Module
SE61 R/3 Documentation
SE62 Industry utilities
SE63 Translate Short/Long Text.
SE63 Translation
SE64 Terminology
SE65 R/3 documents. Short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68 Translation Administration
SE71 SAPscript layout set
SE71 SAPscript Layouts Create/Change
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE80 Repository Browser: Initial Screen.
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Dictionary Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE91 Maintain Messages
SE92 Maintain system log messages
SE93 Maintain Transaction Codes
SE93 Maintain Transaction.
SEU Object Browser
SHD0 Transaction variant maintenance
SM04 Overview of Users (cancel/delete sessions)
SM04 Overview of Users.
SM12 Deletion of lock entries (in the event you have you are locked out).
SM12 Lock table entries (unlock locked tables)
SM21 View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30 Maintain Table Views.
SM31 Table Maintenance
SM32 Table maintenance
SM35 View Batch Input Sessions
SM37 View background jobs
SM50 Process Overview.
SM51 Delete jobs from system (BDC)
SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN Display the menu path to get to a transaction
SMOD/CMOD Transactions for processing/editing/activating new customer enhancements.
SNRO Object browser for number range maintenance.
SPRO Start SAP IMG (Implementation Guide).
SQ00 ABAP/4 Query: Start Queries
SQ01 ABAP/4 Query: Maintain Queries
SQ02 ABAP/4 Query: Maintain Funct. Areas
SQ03 ABAP/4 Query: Maintain User Groups
SQ07 ABAP/4 Query: Language Comparison
ST05 Trace SQL Database Requests.
SU53 Display Authorization Values for User.
Human Resources
PA03 Change Payroll control record
PA20 Display PA Infotypes
PA30 Create/Change PA Infotypes
PP02 Quick Entry for PD object creation
PU00 Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.
Sales and Distribution (SD)
OLSD Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data
VA01 Create Sales/Returns Order Initial Screen
VB21 Transaction for Volume Lease Purchases (done as a sales deal)
VK15 Transaction used to enter multiple sales conditions (most will be entered here)
VL02 Deliveries
SAP Office
SO00 send a note through SAP, can be sent to Internet, X400, etc
Financial Accounting (FI)
FGRP Report Writer screen
FM12 View blocked documents by user
FST2 Insert language specific name for G/L account.
FST3 Display G/L account name.
KEA0 Maintain operating concern.
KEKE Activate CO-PA.
KEKK Assign operating concern.
KL04 Delete activity type.
KS04 Delete a cost centre.
KSH2 Change cost centre group delete.
OBR2 Deletion program for customers, vendors, G/L accounts.
OKC5 Cost element/cost element group deletion.
OKE1 Delete transaction data.
OKE2 Delete a profit centre.
OKI1 Determine Activity Number: Activity Types (Assignment of material number/service to activity type)
OMZ1 Definition of partner roles.
OMZ2 Language dependent key reassignment for partner roles.
Material Management (MM)
MM06 Flag material for deletion.
OLMS materials management configuration menu, most of the stuff under this menu is not under the implementation guide
MM configuration transactions
OLMB Inventory management/Physical Inventory
OLMD MM Consumption-Based Planning
OLME MM Purchasing
OLML Warehouse Management
OLMR Invoice Verification
OLMS Material Master data
OLMW MM Valuation/Account Assignment
Configuration related
OLE OLE demo transaction
OLI0 C Plant Maintenance Master Data
OLI1 Set Up INVCO for Material Movements
OLI8 Set Up SIS for Deliveries
OLIA C Maintenance Processing
OLIP C Plant Maintenance Planning
OLIQ New set-up of QM info system
OLIX Set Up Copying/Deleting of Versions
OLIY Set Up Deletion of SIS/Inter.Storage
OLIZ Stat Set Up INVCO: Invoice Verify
OLM2 Customizing: Volume-Based Rebates
OLMB C RM-MAT Inventory Management Menu
OLMD C RM-MAT MRP Menu
OLME C MM Menu: Purchasing
OLML C MM Menu for Warehouse Management
OLMR C RM-MAT Menu: Invoice Verification
OLMS C RM-MAT Master Data Menu
OLMW C RM-MAT Valuation/Acct. Asset. Menu
OLPA SOP Configuration
OLPE Sales order value
OLPF SPRO Start SAP IMG (Implementation Guide).
OLPK Customizing for capacity planning
OLPR Project System Options
OLPS Customizing Basic Data
OLPV Customizing: Std. Value Calculation
OLQB C QM QM in Procurement
OLQI Analysis OLVD C SD Shipping Menu
OLVF C SD Billing Menu
OLQM Customizing QM Quality Notifications
OLQS C QM Menu Basic Data
OLQW C QM Inspection Management
OLQZ Quality Certificates
OLS1 Customizing for Rebates
OLSD Customizing: SD
OLVA C SD Sales Menu
OLVS C SD Menu for Master Data
Regards,
Pavan -
Hi gurus,
is there any way of printing a date onto the PO-printout that differs from the document date?
E.g. PO is created on Aug 5, 2008. So, the document date is (and has to be!) Aug 5, 2008. But the date on the printed order document should be e.g. Aug 10, 2008.
Can this be achieved without modification?
Thanks in advance
AliciaHi,
It is not possible w/o ABAP help or w/o program modification.
You can use any field at Header Level in PO to maintain this date and print it in PO by making changes in PO Print layout (Smartform or SAPScript)
For e.g. you can use field Validity start under "Additional Data" tab. -
can you please tell me &VBDKL-BRGEW(I13)& what (I13) signifies regarding the layout set in sapscript in?i am beginner ?thank you.
Hi,
this way it will only print the first 13 characters of the field VBDKL-BRGEW.
Also check this
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/d6/0db357494511d182b70000e829fbfe/content.htm">link</a>
Kostas
Message was edited by:
Kostas Tsioubris
Message was edited by:
Kostas Tsioubris -
Hi all,
I'm a bit confused in using the transaction codes in ABAP like se11,...so on.
What code can be used for what application....so on.?
Can any one please help me out in giving the transaction codes in ABAP.
Please give them in a list wise...i.e.,
Transaction code -
What Application(such as editor, smartforms, function modules).
ID: [email protected]
Bye,
SAI KUMARHI,
USMM Pressing F8 will display all hotpacks applied.
SEARCH_SAP_MENU Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
DI02 ABAP/4 Repository Information System: Tables.
LSMW Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.
OSS1 SAP Online Service System
OY19 Compare Tables
SM13 Update monitor. Will show update tasks status. Very useful to determine why an update failed.
S001 ABAP Development Workbench
S001 ABAP/4 Development Weorkbench. (from [email protected])
S002 System Administration. (from [email protected])
SA38 Execute a program. (from [email protected])
SCAT Computer Aided Test Tool
SCU0 Compare Tables
SE01 Old Transport & Corrections screen
SE03 Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09 Workbench Organizer
SE10 New Transport & Correction screen
SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12 Dictionary: Initial Screen - enter object name. (from [email protected])
SE13 Access tables in ABAP/4 Dictionary. (from [email protected])
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser: Initial Screen. (from [email protected])
SE16N Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.
SE17 General Table Display
SE24 Class Builder
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE48 Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.
SE49 Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.
SE51 Screen Painter: Initial Screen. (from [email protected])
SE54 Generate View Maintenance Module
SE61 R/3 Documentation
SE62 Industry utilities
SE63 Translation
SE64 Terminology
SE65 R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68 Translation Administration
SE71 SAPscript layout set
SE71 SAPScript Layouts Create/Change
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE83 Reuse Library. Provided by Smiho Mathew.
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Dictionary Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE91 Maintain Messages
SE92 Maintain system log messages
SE93 Maintain Transaction. (from [email protected])
SEARCH_SAP_MENU From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SEU Object Browser
SHD0 Transaction variant maintenance
SM04 Overview of Users (cancel/delete sessions)
SM12 Lock table entries (unlock locked tables)
SM21 View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30 Maintain Table Views. (from [email protected])
SM31 Table Maintenance
SM32 Table maintenance
SM35 View Batch Input Sessions
SM37 View background jobs
SM50 Process Overview. (from [email protected])
SM51 Delete jobs from system (BDC)
SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN Display the menu path to get to a transaction
SMOD/CMOD Transactions for processing/editing/activating new customer enhancements.
SNRO Object browser for number range maintenance. (from [email protected])
SPRO Start SAP IMG (Implementation Guide). (from [email protected])
SQ00 ABAP/4 Query: Start Queries
SQ01 ABAP/4 Query: Maintain Queries
SQ02 ABAP/4 Query: Maintain Funct. Areas
SQ03 ABAP/4 Query: Maintain User Groups
(Queries,Funct. Areas,User Groups are stored in table AQGQDOC and AQLQDOC )
SQ07 ABAP/4 Query: Language Comparison
ST05 Trace SQL Database Requests. (from [email protected])
ST22 ABAP Dump analysis
SU53 Display Authorization Values for User. (from [email protected])
WEDI EDI Menu. IDOC and EDI base.
WE02 Display an IDOC
WE07 IDOC Statistics
rgds,
bharat. -
after running a bdc program in backgruond nexty day morning whe n u see the reults few records r not updated (error records) what will u do then ?how will u handle the error records
2
what is the differencew b/w report andscripts
an sscripts and smart forms1) u can shedule that bdc program for the error records by correcting the error in the flat file.
2) report is just siple executable program in sap and sapscript is used to design layout like for billing doc each company wil have its layout with its comp logo n other stuff using sapscript u can design it
smartforms are adcance of sapscript and is also used for designing layout its much easier to work on an smartform coding is less n with less time we can design an layout u can also migrate the layout designed in sapscript into smartform
major diff b/w smartforms n sapscript it that
sapscript is cleint dependent n smartform is client independent
sapscript we dont have color fonts n in smartforms we have color fonts
if this inform is usefull pls reward
ravi -
Data is not printing in Print but which is working in print preview
Hi Experts,
When I give print preview the date is displaying fine. But if i give print for that it is not printing the date .
This is in SAP script through some tcode: IW32.
Can you please suggest me what is the issue ? I have checked for all the conditions if are there any .
Thank you in advance.Hi shridhar,
As far i get your issue, the date being displayed in print preview mode is NOT printed when you print it in a paper.
Since I dont see the actual layout of your sapscripts, I suggest the following:
1. Previewing Form is sometimes different when actually printed due to Printer limitations(ex. margins defined to that printer)
2. In order to test if your date is printed in your paper successfully, try to re-position the window where it was. Then try printing it again.
3. If this is successful, then position it not near the edge of your form. If no, this means that you need to manipulate your date value such as passing it in a char datatype then try to display it again.
Hope it helps. Cheers -
Important transaction codes and guidelines ...
Hi to all
Please tell me what are the things that a person should keep in mind while working in realtime servers.
What are the transaction codes , programs which are most commonly used.
Please send me as I have newly joined a company.
Thanks ...Hi
may be this can help..
BASIS/ABAP
SEARCH_SAP_MENU Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.
DI02 ABAP/4 Repository Information System: Tables.
LSMW Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.
OSS1 SAP Online Service System
OY19 Compare Tables
SM13 Update monitor. Will show update tasks status. Very useful to determine why an update failed.
S001 ABAP Development Workbench
S001 ABAP/4 Development Weorkbench. (from [email protected])
S002 System Administration. (from [email protected])
SA38 Execute a program. (from [email protected])
SCAT Computer Aided Test Tool
SCU0 Compare Tables
SE01 Old Transport & Corrections screen
SE03 Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.
SE09 Workbench Organizer
SE10 New Transport & Correction screen
SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
SE12 Dictionary: Initial Screen - enter object name. (from [email protected])
SE13 Access tables in ABAP/4 Dictionary. (from [email protected])
SE14 Utilities for Dictionary Tables
SE15 ABAP/4 Repository Information System
SE16 Data Browser: Initial Screen. (from [email protected])
SE16N Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.
SE17 General Table Display
SE24 Class Builder
SE30 ABAP/4 Runtime Analysis
SE32 ABAP/4 Text Element Maintenance
SE35 ABAP/4 Dialog Modules
SE36 ABAP/4: Logical Databases
SE37 ABAP/4 Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE41 Menu Painter
SE43 Maintain Area Menu
SE48 Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.
SE49 Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.
SE51 Screen Painter: Initial Screen. (from [email protected])
SE54 Generate View Maintenance Module
SE61 R/3 Documentation
SE62 Industry utilities
SE63 Translation
SE64 Terminology
SE65 R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)
SE68 Translation Administration
SE71 SAPscript layout set
SE71 SAPScript Layouts Create/Change
SE72 SAPscript styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript Translation Layout Sets
SE77 SAPscript Translation Styles
SE80 ABAP/4 Development Workbench
SE81 SAP Application Hierarchy
SE82 Customer Application Hierarchy
SE83 Reuse Library. Provided by Smiho Mathew.
SE84 ABAP/4 Repository Information System
SE85 ABAP/4 Dictionary Information System
SE86 ABAP/4 Repository Information System
SE87 Data Modeler Information System
SE88 Development Coordination Info System
SE91 Maintain Messages
SE92 Maintain system log messages
SE93 Maintain Transaction. (from [email protected])
SEARCH_SAP_MENU From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.
SEU Object Browser
SHD0 Transaction variant maintenance
SM04 Overview of Users (cancel/delete sessions)
SM12 Lock table entries (unlock locked tables)
SM21 View the system log, very useful when you get a short dump. Provides much more info than short dump
SM30 Maintain Table Views. (from [email protected])
SM31 Table Maintenance
SM32 Table maintenance
SM33 Display Table Parameter ID TAB
SM35 View Batch Input Sessions
SM37 View background jobs
SM50 Process Overview. (from [email protected])
SM51 Delete jobs from system (BDC)
SM62 Display/Maintain events in SAP, also use function BP_EVENT_RAISE
SMEN Display the menu path to get to a transaction
SMOD Transactions for processing/editing/activating new customer enhancements.
CMOD Transactions for processing/editing/activating new customer enhancements.
SNRO Object browser for number range maintenance. (from [email protected])
SPRO Start SAP IMG (Implementation Guide). (from [email protected])
SQ00 ABAP/4 Query: Start Queries
SQ01 ABAP/4 Query: Maintain Queries
SQ02 ABAP/4 Query: Maintain Funct. Areas
SQ03 ABAP/4 Query: Maintain User Groups
SQ07 ABAP/4 Query: Language Comparison
ST05 Trace SQL Database Requests. (from [email protected])
ST22 ABAP Dump analysis
SU53 Display Authorization Values for User. (from [email protected])
PFCG Role maintenance
SU21 List of object classes
WEDI EDI Menu. IDOC and EDI base.
WE02 Display an IDOC
WE07 IDOC Statistics
Cheers
VJ -
Print Form after Defect Recording
Hi,
I have a requirement to print a so called Incoming Rejection Form. This form is printed after doing the defect recording.
Is there a standard way to print a form after saving defect recording?
Thanks,
RaymondHi
check the FORM ....you have either made changes or create a new form
check following
A form definition contains the following elements:
Header data:
This is general information about the form, such as the user ID of the person who created it, a short text describing the form, and global control data, such as font used and page format.
Paragraphs:
Paragraphs are the real layout elements in SAPscript. Every text entered in the editor consists of various paragraphs. The beginning of a paragraph is indicated by a paragraph tag in the left column of the editor. Paragraph names and attributes are defined in the form.
Characteristics or attributes which can be defined for paragraphs include text alignment, line spacing, font used etc.
Character strings:
Character strings are layout elements relevant for a section of text within a paragraph. They are inserted in the continuous text. The beginning of a section of text is marked with the character combination <XX> and the end with </>. Here XX is the name of the character string, which is defined in the form.
Windows:
Windows represent logical units. Although they do not have a physical position on the page, they have a name which reflects the purpose of the text to be displayed in the window. For example, an address window, a window for a letter header etc.
A window type is assigned to every window. The most important type is the main window. "Continuous" text appears in the main window. The text can therefore extend over the main windows of several pages. The other window types, on the other hand, do not allow text which does not fit in the window to be continued in the window on a subsequent page.
Pages:
One or more pages which are to appear in the form are defined here. The attributes of a page include the name of the next page and the type of page numbering. The user determines the page sequence by specifying the next page and defining the first page of the form in the header data.
Page windows:
A page window is defined by specifying the position and size of a form window on a form page. The page window describes the position of a window on a specific page of the form and therefore the area in which text can be output in the form.
Maybe you are looking for
-
I have licences for Illustrator and Flash now. If I upgrade to Creative Cloud, and then at some point in the future cancel my subscription, will I still be able to use the Illustrator and Flash that I have now? I don't mind reinstalling them, but I
-
Charges in PO without excise duty
Dear Gurus, How to incorporate a condition type of charges (let say packaging and frwding charges ) , on this excise duty is not applicable , so how to exclude this from the net price calculaiton , as the net price only used as the base value for the
-
Hello all, I have a friend who wanted to help me out with movies off his Ipod so that I may be able to watch them while I am deployed to Iraq. Unfortunately, I do not know how to open these files to get them to play in itunes. Does anyone know what t
-
Authentication error after upgrade to APEX 4.2
Hi, After the upgrade to Apex 4.2, I started to receive an error when trying to run the application. ERROR: "There is no authentication configured for this application. ORA-01403: no data found". I checked and double checked the authentication option
-
I'm making my first Time Machine backup of my PowerBook G4 since installing Leopard. There is 74.41 GB of data on my main hard drive (Mac OS Extended), but Time Machine says that it is taking 49.9 GB for the backup on my external backup drive. I unde