Billing output dump analysis

Hi,
While taking print out of the invoice correction billing type, system is giving dump.
The dump error analysis displayed following message-
" In the current programme "ABCDE123", an arethmetic operation ('divide','/','div',or 'mod') with a type P operand attemptde to divide by 0."
What does this mean and how this error can be removed?
Pls. guide.
Points will be rewarded.
Regards

hi
if you feel this answer solve your query please reward with points
You can solve this through the transaction code st22 and analyse the error with your abaper fix the solution
thanks & Regards
Rack29

Similar Messages

Delivery Output & Billing Output

Hi All,
Are there any standard transactions for Delivery and billing ouputs, other than VL02N & VF02
So that user can view and take print outs of only those documents.
Thanks & Rgds
Naveen

Hi Naveen
DELIVERY OUTPUT:
VL71    Output from Outbound Deliveries
VL74    Output from Handling Units
VL70    Output From Picking Lists
VL75    Shipping Notification Output
FOR GENERAL TRANSACTION CODE REFER BELOW:
VL02N    Change delivery document
VL04    Delivery due list
VKM5    List of deliveries
VL06G    List of outbound deliveries for goods issue
VL06P    List of outbound deliveries for picking
VL09    Cancel goods issue
VT02N    Change shipment
VT70    Output for shipments
BILLING:
VF02    Change billing document
VF11    Cancel Billing document
VF04    Billing due list
FBL5N    Display Customer invoices by line
FBL1N    Display Vendor invoices by line
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04    Delivery due list. Run the delivery due with your order number to create the delivery
LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N    Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
FOR ALL THE REQUIREMENT:
Transactions
search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
VOE1    Translation between EDI categories and SD item categories
VOE2    Table EDSC view. Customer link to sales area detail
VOE3    Table view EDPVW. Add partner types that will be transferred to the IDoc
VOE4    Table view EDPAR. Link external partner number with our internal number
WEDI    EDI Administrator Menu
BALE       Idoc Administration
Scheduling agreements
OVA9    Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
OVAI    Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
OVAJ    If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
WE09 / WE02    IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05    View IDocs
WE19    EDI test tool. Use to test inbound Function module changes.
WE20    Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30    Create IDoc extension type
WE31    Segment create
WE57    Assign function module to logical message and IDoc type
WE60    IDoc type documentation tool
WE82    Link Release detail to Extension IDoc Type
BD55    Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87    Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA    ALE Application Distribution
BALM    ALE Master Data Distribution
Output determination
856 - ASN
V/36   Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 V7ALLE SHAD for grouped ASNs. I.e. Group deliveries into shipments
VV21,VV22,VV23   Create output condition records for shipping. LAVA WE (Partner function) - We must add each new partner with VV21
VL71   Reissue output for deliveries
810 - Invoice
V/54   Maintain access sequence for billing documents
VV31,VV32,VV33   Create condition records for billing documents. (RD00 RE Billing party)
VF31   Reissue output for billing documents
855 Order Response
V/30   Sales document output types (BA00)
V/48, V/32, V/43   Maintain access sequence for sales documents
VV11,VV12,VV13   Create condition records for sales documents. (BA00 SP Sold to party)
Requirements coding
V/27    Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
VA02    Sales order change
VA05    List of sales orders
VA22    Quotation change
VA32    Scheduling agreement change
VA42    Contract change
Billing
VF02    Change billing document
VF11    Cancel Billing document
VF04    Billing due list
FBL5N    Display Customer invoices by line
FBL1N    Display Vendor invoices by line
Delivery
VL02N    Change delivery document
VL04    Delivery due list
VKM5    List of deliveries
VL06G    List of outbound deliveries for goods issue
VL06P    List of outbound deliveries for picking
VL09    Cancel goods issue
VT02N    Change shipment
VT70    Output for shipments
General
VKM3, VKM4    List of sales documents
VKM1    List of blocked SD documents
VD52    Material Determination
Workflow
SWEAD    Event queue administration
SWE2    Event type linkages
SWE3    Event linkages
PPOME    Organizational Unit Maintenance
SWE5    Consistency Checks for Event Linkages
SWUD    Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04    Delivery due list. Run the delivery due with your order number to create the delivery
LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N    Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
ME22N      PO Change
ME57         Create PO from purchase requisition
Goods Movement
MIGO    Post goods receipt
Other
MD04    Material Requirements. Shows material requirements and releases against materials
SE38    ABAP Editor. Used to modify ABAP programs
SM01    Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
SHDB    Transaction recorder (BDC)
CMOD    User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
SE16    Table contents display
SOST    View mails sent externally from SAP
SU53    Check authorization object
SQVI    Table Quickviewer Used to created quick client dependent reports
ST22    ABAP Dump Analysis
ST01    System trace
ST11   Display developer trace
ST05          SQL Trace
SM21          System log
ST22           Display short dumps
SM12          Display locked entries
Programs
List of ABAP Reports
Idoc
RBDAPP01   Post inbound Idocs to application documents
RBDAGAI2   Re-processing of IDocs after ALE input error
RBDAGAIE   Reprocessing of edited IDocs
RBDMANIN   Start error handling for non-posted Idocs
RSEINB00   Idoc inbound processing by file
RSEOUT00   Process outbound IDocs
General
RV80HGEN    Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
RSWUWFML    Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status' sent from SAP.
RHSOBJCH    Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
**Error** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
RSPO0075    Run report RSPO0075 to activate access method M for device types.
Reward if useful to u
Message was edited by:
        narendran vajravelu

Billing output YCTD for rebate

hi,
I have a problem with the billing output YCTD appearing for lump sum agreements.
Is there any way i can reconfigure this output type so it does not appear for the billing type?
points will be rewarded generously

hello,
if you have an output in a document, it was probably found based on the condition technik. To check how the system found this output, choose goto -->header --> output. On the following screen in the Goto menu, you find the determination analysis.
Once you no how the output got into your document, you can change your output determination settings, so it won't appear again:
SD Customizing, Basic functions, Output determination, maintain output det. for billing docs.
Here you can change the procedure or the accesses.
It is also possible to set up your own condition: 'if document type=something, YCTD cannot be processed'.
If you have further questions, just ask.
Balazs

What is Short Dump Analysis and secendry index ?

Dear Experts .
1.) What is purpose of T-codes SE30 and ST22 ?
What is Short Dump Analysis ?
2.) What is secendry index , How to use it ? How it effects the Performance of a report ?
Please it is urgent ...
Regards : Rajneesh

Hi
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

Error in HRPAD31 ( Short dump Analysis )

Hi friends,
When i am changing the existing qualification or adding new qualification it is showing this error in short dump
Pls advise me if there is some relationship i am missing in 031 ?
here is the description of short dump
Runtime Error DBIF_RSQL_SQL_ERROR
Exception        CX_SY_OPEN_SQL_DB
Occurred on     10.09.2008 at   10:48:39
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', wasneither
caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"
Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure "ADATA_DB"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"
Internal call code.........: "RSQL/INSR/HRPAD31"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself, use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLRHAP" or "LRHAPF1K"
"ADATA_DB"
System environment
SAP Release.............. "620"
Application server....... "Development"
Network address.......... "200.200.200.10"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "Development"
Database type............ "ORACLE"
Database name............ "VC3"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 16 2007 23:23:39"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
User, transaction...
Client.............. 600
User................ "HUSER"
Language key........ "E"
Transaction......... "PP01 "
Program............. "SAPLRHAP"
Screen.............. "MP100100 6000"
Screen line......... 16
Information on where terminated
The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".
The main program was "MP100100 ".
The termination occurred in line 57 of the source code of the (Include) program LRHAPF1K"
of the source code of program "LRHAPF1K" (when calling the editor 570).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.
The procedure is in the program "SAPLRHAP ". Its source code starts in line 8 of the (Include) program "LRHAPF1K ".
PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?

Hi Ted,
It is working, i just logged off and logged in. Now there is no error.
Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
I appreciate on more time for your knowledge.
I have rewarded the points also....
Regards
HR user

Need info on Billing Outputs

Hello,
I need info abt billing Outputs - The language is maintained in Bill to party (Customer master), Its maintained in Condition record, It can be changed while creating the invoice.
Now my question is, which of the above three cases has got highest priority.
Could some one provide me some info on this?
Regards,
Krishna

By default, we will maintain language in Bill-to-Party & also Condition record. But if required, it can be chaged at Invoicing level while taking output. Priority will be Bill-to-party, followed by Condition Record.
Regards,
Rajesh Banka

EDI billing outputs are capturing credit memos as well as invoices

I am a newcomer to the company I am currently with, and to this forum, and I have 6 years of experience in EDI and SAP SD.
I am working on a project to determine why our EDI billing outputs are capturing credit memos as well as invoices, and attempting to send them by EDI, causing failures in our Seeburger translator. Most customers donu2019t want credit memos by EDI. My goal is to track backwards and determine what portion of the EDI process in SAP is pulling credit memos rather than just invoices. I suspect that someone intentionally made changes in the past to put this in place, but we need to have a message type that includes invoices and credit memos, to be attached to specific partners that want this, and another more standard message type that sends only invoices.
The message control for the example partner specifies Message Type ZURH (customized by this company for some reason), Application V3 (which seems standard), and process code SD09 (which seems standard). Could someone help me to navigate to an area where I may be able to find out what parameters are used to determine what transaction types are pulled to be sent out by EDI for billing? I suspect that the issue may be in Application V3, but I am unable to find any help to view u2018Applicationsu2019, because application is such a widely used word.
How can I display/change Application V3, in order to check itu2019s contents?
Any other ideas why credit memos may be included would be appreciated, and I always appreciate having the transaction codes mentioned as well.
Thank you in advance for your assistance.
Application V3 (what specifies what transaction type this pulls?)
Message Type ZURH,
Process Code SD09.
Access Sequence used is ZSD1 Billing Documents (Access Sequence ZSD1 does not appear in transaction V/48 (?))
Transmission Medium is 6 EDI.
The program is RSNASTED, and the FORM Routine is EDI_PROCESSING.

Satish,
Thanks for the suggestions.
I checked transaction VV33 u201CDisplay Output Condition Records: Billingu201D for Output Type ZURH, Key Combination Sales Org/Payer, and I find the example customer linked to ZURH, as I would expect (5010013645     BEST BUY CANADA Vendor #41448     PY          6     1).
I donu2019t see any data about specific transaction types such as credit memos or invoices, so I may not be looking in the right place. I donu2019t find entries under any other key combination. How would I check if Output Condition records are maintained for credit memos?
In regards to the output type being assigned to the credit memo billing type (ZG2U), Iu2019m afraid I donu2019t know how to check that either.
In NACE, I see that u2018Proceduresu2019 list the CTyp (?), and procedure US0001 is the only one that includes credits and debits. I donu2019t recognize the Ctyps ZDN0 and ZCN0. The billing type is ZG2U, which I don't see in any of the Procedures:
10     1     RD00     Invoice
20     2     ZPRO     Proforma Invoice
30     1     ZCAN     Canadian Cust. Inv
40     1     ZCOM     Commercial Invoice
50     1     ZDN0     Debit Note
60     1     ZCN0     Credit Note
How would I be able tell which u2018Procedureu2019 is being used for Application V3, and how would I change that to another Procedure for testing?

Create Billing Output from VA01

Hi everyone!
I wonder is it possible to create an invoice with billing output immediately?
I usually use create sales order VA01, create billing due list VF04, create billing output VF31;
I'd prefer to be able to key on an invocie and for it to create a billing document in my spool right away without having to wait on the overnight process or manually pushing it using VF04 & VF31.
Any ideas?
Many many thanks!!!
Ciara

Hi,
For this change to appear we have to go for some seetings.They are mentioned below.
1.Goto the T.Code "NACE".
Select the application as "V3(Billing)".
Click on "Output types".
Select your output type.
Click on "Details" or Press "CtrlShiftF2".
Maintain the value as "4(Send Immediately(when saving the application))" for the field "Despatch time".
Check the value for transmission meduim.Ithink it is "1(Print output)".
Save.
2.Goto the T.Code "VV31".
Enter your output type.
Press Enter.Select your valid condition table if multiple tables exists.
Enter.
Maintain the valid values.Select that maintained entry.
Click on "Communication".
Maintain the output device as "LOCL".
And also check the box "Print Immediately".
Save.
If you create the invoice by using VF01,then the out put will be triggered automatically.
Or Goto T.Code VA02/VA01.After entering al the values,Click on "Sales document" in th emenu bar and then click on "Billing".
Even in this case also output will be triggered automatically.
If you want,then you can reprocess this output by using the T.Code "VF01",by selecting the processing mode as "2".
Regards,
Krishna.

Billing, output, invoice consolidation

Hello friends, I am looking for a document on Billing and output .invoice consolidation.....I cant understand from Standard SAP materiel....so if u have made some document for your reference please share it with me...
Please E-mail me the matereriel on [email protected]
Thanks in advance !!
Best regards,
Lata

Sent the required info to the email given..
Please do check and see if it helps..................
edit : : for some reason my email has bounced back..
here's the stuff..do please refer :
Info on billingsap help documents---- http://help.sap.com/saphelp_nw04/helpdata/en/e9/ce268db69b11d2956c00a0c93029cf/frameset.htm
For billing output refer these: Set up output condition for billing document.
Output type determination in Billing document
A good information PDF file on the Billing document consolidation: http://www.saptechsolutions.com/pdf/SDBillingDocumentConsolidationAndSplit.pdf
regards
Poorna
Edited by: Poorna Yalamanchili on Feb 20, 2008 2:57 AM

Billing output by mail changing the subject line

HI,
i am sending the billing output by email, but the subject of the email getting changed regularly. my requirement is i have to set standard subject for all billing output by mail.
Reagrds
Muthuraman.D

Go to Tcode - NACE - Choose V3 - Choose 'output types' on the application toolbar
- select output type - 'double click on mail and texts' at left hand side. See if you can add anything there and checck the mail.

Send the billing output by e-mail for the user

Hi,
Can you tell me if it's possible to send the billing output by e-mail (Medium = 5 - External send) for the user that create the billing document? the e-mail of the user is in SU01D.
Thanks in advance
Dora

Hi Dora,
What you can do is when you want to send a mail to customer after you receive the email for bill is do the following settings.
1) Create a condition record VV31 with the required Key combination where you can give the name of the Employee or end user with the email id.
2) Select the trasmission medium as 7 ( Simple Mail)
3) Once the Billing is done E-Mail will be triggered.
4) Downlaod it or forward it to your client with the additional text in the E-Mail.
Hope this helps.
Thanks and Regards
Rohit Dujari

Output determination analysis for Handling Unit

Hi Friends,
Can any body help me on how to check the output determination analysis for Handling unit outputs.
I tried checking the document flow through delivery of the Handling unit but could not check.
thank you for your help in advance.

Hi,
Try in t-code VL74 - Output from HU...
enter ur selection parameters like Output Type,Transmission Medium,Sort order and Processing mode
once you execute select the entries and click on Log (shift+F6) icon...
Reg,
JJ

Output Determination Analysis in Std SAP

Hi all,
Is there any Output Type which doesn't have an Output Determination Analysis in standard SAP?
Regards,
Ravikumar

Hi Ravi kumar
Output Determination Analysis will be there for all output types if you do output determination.as it is a condition technique But why you dont want to have Output Determination Analysis? what is your requirement
Bit if you do the condition technique in output for all output types then you wont be facing the problem of Output Determination Analysis
Regards
Srinath

Output determination analysis

In output determination analysis I am getting single output type three times with different messages.
Any one can please through some light on this.

Hi,
Please make your condition records in the Access Sequence exclusive and check.
Reward points if it helps.
Regards,
Harsh

How to do DUMP Analysis ?

How to do DUMP Analysis ?Can anybody explain me the steps to solve the dump step by step ?
thanks
Naresh

Hi
A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
The snapshot contains the following information:
Why the program has terminated
What caused the program termination
Where in the program code the termination occurred
What you can do to correct the error
The values of the relevant system fields when the program terminated
The calls or events that were active when the program terminated
Any other programs that are affected.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

Billing output dump analysis

Similar Messages

Maybe you are looking for