What is the use of internal document number in excise invoice

Hi All,
Could you please explain the use of "Internal Document" number in Excise invoice.
Regards,
Mullairaja

As you would be aware for all types of Excise Transactions like DLFC (for normal sales), GRPO (for goods receiving) etc., system will generate an internal number which is only for reference and this will be a continuous number irrespective of excise transaction type.
For example, if you generate a sale order, the excise transaction type would be DLFC and let us assume the internal number generated by the system is 11 and immediately, if you generate any other excise document other than normal sales, the internal number would be 12. This number range you need to maintain in TCode SNUM for object J_1IINTNUM every year.
thanks
G. Lakshmipathi

Similar Messages

Error while detrmining Internal Document Number for Excise Invoice.

Hello mate, I am trying to create excise invoice for for factory sale. while saving the document I am getting an error" Error
while detrmining Internal Document Number for Excise Invoice. Message: Maintain Number Range for J_1IINTNUM". I have already maintained number range for mentioned object "J_1INTNUM" in TCODE SNUM , still getting error. Please solve my querry . Is it related to transport or number range activation or something else? I have maintained number range with serial no. "01"

Hello ,
Ensure that number ranges are properly maintained in the respective client that should be the year specific.Some times even u maintained the system should not consider that number ranges due to table updation problem ,because i had faced the same in the earlier and received the reply from the sap stating that this error was occured rarely after the years,so please ignore that ,for your problem u first come out of the screen and then re log in and then create the excise invoice ,then check the number ranges .
Please revert for any
Kalyan

What is the system variables of document number in General Ledger PLD?

Dear all,
Would anybody kindly tell me what is the system variables of document number in General Ledger Print Layout Designer?
The default print layout use transaction number (system variables 272), however, my client wants document number to be displayed in the transaction number column.
Regards,
Simon Chiu

Hi
The only list available for Supported variables is for the version 2007A and for some specific localizations like Brazil and India.
For the 2007A version the list is available in the following link:
http://service.sap.com/smb/sbo/pld
'How To Use the PLD Variables File in Release 2007 A '
But in general the variables are for documents not for reports.
In this case I believe there's no variable and you may need to fill a requirement in the Forum for that.
Paulo Calado
SAP Business One Forums Team

Use of Official Document number in VAT Books for Italy

Dear All,
I would like to share with you a big doubt I have regarding the use of Official Document Number in the VAT Books. This is a requirement for an Italian client.
According to my clients requierement they would like to manage 5 different VAT Books:
1. Sale book (for all finished products sold in Italy, EU and outside EU)
2. Sale book for sundry sales (CAPEX, services, other goods ...)
3. Purchase book (for all the goods bought in Italy and out-side EU and for all the services bought in Italy)
4. EU purchase book (for all the goods and services bought from EU suppliers and for all the services bought from not EU suppliers)
5. EU sale (reverse charge) book (with the same numbers and amounts of the purchase book number 4)
For every VAT Book they want the Officil Document number to be displayed. Not only that, they want the Official Document Number to end in 1 (XXXXXXX1) at the start of every natural Year for EVERY VAT Book, and have sequential numbering with no gaps.
My intention is to use: RFKKITVATM. This is a specific VAT report for Italian Companies. The report selects documents that contain regular VAT and that have been assigned an Official Document number (ODN). You run this report to generate such a list for the current month. It selects documents with an ODN based on the invoice or credit memo posting date. You can create as many layout-variants (one per VAT Book??).
My question is: The VAT Books are based on different VAT Codes. How can we have every single VAT Book to start with an Official Document number ending in 1? The number range will be Document type dependant and not VAT Code dependant.
As per my knowledger, To use Official Document Numbering (ODN) in Italy we have to make a number of settings:
- Activate ODN
- Specify which document types the system is to assign official document numbers to.
- Assign installation-specific function modules to events
- Define Number ranges
Have you faced up a similar requirement? Is this a legal requierement or is my client mixing up with another legal requierement related to this subject: To print a sequential number and the fiscal year on each page of the reportu2019s output list. The System starts the numbering automatically at 1, as it does for each subsequent year.
Many thanks in advance for your help.

Hello All,
Am facing an issue when implementing the ODN solution for Italy. I cannot replicate the ODN in field BKPF-XBLNR_ALT when posting Invoice via MIRO.
1. I have Defined a Document Class per VAT Book
2. I have Assign a Document Class to Document Types (in my example Document Type "RE" to Document class "43". And select "Generate Official Document Number, with date control".
3. I have mantained Number ranges
4. I have Assign the Number ranges to Document Class.
5. In order to transfer the ODN from Billing docs to Accounting docs I have entered the Document Type "RV" at Billing Document Type level.
It all works as expected except for the Accounting documents coming from Logistic Invoice verification - MIRO transaction. Document Type "RE" is used for posting but my field BKPF-XBLNR on Accounting document remains blank.
Is there any additional step am missing?
Thanks in advance.
Regards,

Accounting document for Export Excise invoice

Dear All,
We have two scenario's one is Domestic Sales & Export Sale.
In domestic sales as per the normal flow of document we create excise invoice after billing document and accounting documents are also generated and updated in the billing document accounting (VF02). Accounting document for excise invoice has been generated.
However in export sales we create excise invoice with the reference of billing document but no accounting document has been generated for excise invoice.
Can u please tell me where i have to make changes so my accounting document for export excise invoice will generate?
Thanks & Regards,
Ratish

Hi ALL,
There are 4 export scenario :
1) Deemed export 2) Export under Bond 3) Export under claim for rebate [No bond] 4) Export under Letter of Undertaking.
3) In export under no bond process is :- we pay the excise on the goods for exports and create the ARE-1 doc and send to port where the customers officials note the actual quantity of goods on the ARE-1 doc and stamped it. Then these stamped ARE-1 will be send to the excise range of the despatch plant(for exports) where we claim the rebate.
Now if you are not able to generate the accounting doc for such a scenario some of the consultants may suggest u to use the user exit (J_1I7_USEREXIT_DUTY_IN_EXPORT) and pass the the value X to the parameter SUPPRESS_CALCULATION this intern will help u to generate the Accounting doc also. but real problem lies somewhere else.
Actual Solution: Maintain J1ID (Customer excise details)
for export customer maintained the excise indicator to 3 {Nil Duty} insted of 1 {100% tax}.
Problem will be solved
Regards
Satish Zade

What is the use of T.Code: FAGLCOFIFLUP - Post CO Documents to FI?

Expects...
What is the use of T.Code: FAGLCOFIFLUP - Post CO Documents to FI
Accounting> Financial Accounting> General Ledger> Corrections> FAGLCOFIFLUP - Post CO Documents to FI
Thanks & Regards
Bhagiradha.P

Hi,
The real-time integration of Controlling with Financial Accounting was active at the time the CO documents were posted.
CO documents could be not transferred to financial accounting on behalf of errors which are only known to occur in the following situations:
- During mass processing such as internal CO assessments or distributions
- Manual posting of individual CO documents is not possible if errors occur in financial accounting.
- If real-time integration was not active when the CO document was posted, you must use the report FAGL_COFI_TRANSFER_CODOCS to transfer these CO documents to financial accounting because they are not in the worklist.
Regards,
Eli

What is the use of Release Strategy for Sales Document

Hi,
Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.

Hi,
Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.
Lowest Status No: Sale Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated; the old status with status number is deactivated. This is only valid under certain conditions. The system makes a note of the status with the highest status number that has been reached up to the present. The "lowest number" of this status number determines which status number a new status must have.
Highest Status No: Sales Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated, the old status with a status number is deactivated, provided the new status number does not exceed the 'highest number' defined for the old status number
If you want more clarity try to check below link
http://www.sapfunctional.com/SD/ReleaseStrategy/Index.htm
Regards,
Prasanna

What is the use of Withholding tax identification number field?

Hello SAP Experts,
I posted this question earlier but had to close because of no replies from anybody. Posting it again to see if I am lucky to get some answer this time.
Can someone tell what is the use of field Withholding Tax Identification Number? Does it help with the reporting? Where does it get populated on the report if given at vendor or master record or within the withholding tax customization for company code? What is the difference between creating it in the customization for withholding tax information for company code and vendor/customer master record?
As per SAP: Withholding tax identification number
This is a number issued by the tax authorities per withholding tax type.
This number must be specified in Customizing either:
(a) As part of the withholding tax information defined for the company code, or
(b) As part of the withholding tax information defined in the customer or vendor master record.

Hi Pete,
The only thing that I could check is the content used in US:
See content of this field for US:
LFA1-STCD1 Social security number
LFA1-STCD2 Employer identification number
LFBW-WT_WTSTCD Withholding tax identification number for WT Type
In order to populate it, please kindly check the following:
The reason why you cannot fill in the field WT_WTSTCD in transaction
Fk02 however you can do it in XK02 (Change vendor centrally) can be due
to wrong customizing of the field status group.
Kindly check the following:
SPRO->
Finantial accounting -> Accounts receivable and accounts payable ->
Define screen layout per activity (vendors) -> Change Vendor(Accounting)
Company code data -> W/holding tax data, w/h tax 2 ->
FIELD Withholding tax code,w/h tax 2 will be probably just available to
display. Please, change it to optional entry.
I hope I could be of assistance.
Kind Regards,
Fernando Evangelista

What is the use of Indicator in defining sales document

HI pls explain what is the use of Indicator in defining sales document

Please go through this thread
[sales document type - field indicator |sales document type - field indicator]
thanks
G. Lakshmipathi

What's the uses of "group" in "Document Numbering".

What is the uses of "group" in "Document Numbering"?
How can we link various "groups" to different "user"?
How can I set, if I want some user to be restricted to a particular series?
Pl Reply asap.
Khushwant

Hi Khushwant
The solution is In the authorisation form,
Go to the following module: Administration >System Initialization>Authorisations -->General Authorisations.
In the Authorisations form select the simple user on the Left collumn and on the right of the form go to Administration --> System Initialization --> Series
There you can determine the user's authorizations on particular series.
Hope this was more helpful
Regards
George

What is the use of FOLDER NODE in SMARTFORMS?

what is the use of FOLDER NODE in SMARTFORMS?
please explain.

Hi,
By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
How to create a New smartfrom, it is having step by step procedure
http://sap.niraj.tripod.com/id67.html
Here is the procedure
1. Create a new smartforms
Transaction code SMARTFORMS
Create new smartforms call ZSMART
2. Define looping process for internal table
Pages and windows
First Page -> Header Window (Cursor at First Page then click Edit -> Node -> Create)
Here, you can specify your title and page numbering
&SFSY-PAGE& (Page 1) of &SFSY-FORMPAGES(Z4.0)& (Total Page)
Main windows -> TABLE -> DATA
In the Loop section, tick Internal table and fill in
ITAB1 (table in ABAP SMARTFORM calling function) INTO ITAB2
3. Define table in smartforms
Global settings :
Form interface
Variable name Type assignment Reference type
ITAB1 TYPE Table Structure
Global definitions
Variable name Type assignment Reference type
ITAB2 TYPE Table Structure
4. To display the data in the form
Make used of the Table Painter and declare the Line Type in Tabstrips Table
e.g. HD_GEN for printing header details,
IT_GEN for printing data details.
You have to specify the Line Type in your Text elements in the Tabstrips Output options.
Tick the New Line and specify the Line Type for outputting the data.
Declare your output fields in Text elements
Tabstrips - Output Options
For different fonts use this Style : IDWTCERTSTYLE
For Quantity or Amout you can used this variable &GS_ITAB-AMOUNT(12.2)&
5. Calling SMARTFORMS from your ABAP program
REPORT ZSMARTFORM.
Calling SMARTFORMS from your ABAP program.
Collecting all the table data in your program, and pass once to SMARTFORMS
SMARTFORMS
Declare your table type in :-
Global Settings -> Form Interface
Global Definintions -> Global Data
Main Window -> Table -> DATA
Written by : SAP Hints and Tips on Configuration and ABAP/4 Programming
http://sapr3.tripod.com
TABLES: MKPF.
DATA: FM_NAME TYPE RS38L_FNAM.
DATA: BEGIN OF INT_MKPF OCCURS 0.
INCLUDE STRUCTURE MKPF.
DATA: END OF INT_MKPF.
SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
MOVE-CORRESPONDING MKPF TO INT_MKPF.
APPEND INT_MKPF.
ENDSELECT.
At the end of your program.
Passing data to SMARTFORMS
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
formname = 'ZSMARTFORM'
VARIANT = ' '
DIRECT_CALL = ' '
IMPORTING
FM_NAME = FM_NAME
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
if sy-subrc <> 0.
WRITE: / 'ERROR 1'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function FM_NAME
EXPORTING
ARCHIVE_INDEX =
ARCHIVE_INDEX_TAB =
ARCHIVE_PARAMETERS =
CONTROL_PARAMETERS =
MAIL_APPL_OBJ =
MAIL_RECIPIENT =
MAIL_SENDER =
OUTPUT_OPTIONS =
USER_SETTINGS = 'X'
IMPORTING
DOCUMENT_OUTPUT_INFO =
JOB_OUTPUT_INFO =
JOB_OUTPUT_OPTIONS =
TABLES
GS_MKPF = INT_MKPF
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
for Smartforms material
http://www.sap-basis-abap.com/sapsf001.htm
http://www.sap-press.com/downloads/h955_preview.pdf
http://www.ossincorp.com/Black_Box/Black_Box_2.htm
http://www.sap-img.com/smartforms/sap-smart-forms.htm
http://www.sap-img.com/smartforms/smartform-tutorial.htm
http://www.sapgenie.com/abap/smartforms.htm
How to trace smartform
http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
http://www.sap-img.com/smartforms/smart-006.htm
http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
Re: Need FAQ's
check most imp link
http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
step by step good ex link is....
http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
Reward all helpfull answers
Regards
Omkar

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

What is the use of SWIFT CODE IN BANK ACCOUNTS

What is the use of SWIFT CODE IN BANK ACCOUNTS

HI kishore,
The SWIFT code is used for identifying banks in international payment transactions.
see these links for your refernece
http://sapexperts.blogspot.com/2007/01/bank-accounts.html
http://www.answers.com/topic/international-bank-account-number
thanks
karthik

What is the use of keyword SCAN ABAP-SOURCE

Hello experts,
what is the use of scan abap-source. please explain. what is tokens, statements, levels in that.

Hi
SCAN
This statement is for internal use only.
It cannot be used in application programs.
SCAN ABAP-SOURCE itab1 ...TOKENS INTO itab2
 ...STATEMENTS INTO itab3.
Parts marked with " ..." are interchangeable
Addition 1
... FROM n1
Addition 2
... TO n2
Breaks down the source code table itab1 into tokens not from start to finish, but only from line n1 to line n2.
The additions FROM n1 and TO n2 must, in this order, follow the specification of the source code table itab1.
When using the start specification n1, use the addition WITHOUT TRMAC to ensure that there are no unnecessary database accesses to the table TRMAC.
The end specification n2 is treated as "soft", i.e. a statement that begins on a line <= n2, but ends only on a line > n2, is returned completely.
If the end specification n2 is split in a chain statement, only the split part up to the next comma is returned completely, not the entire chain statement up to the next period.
Negative line specifications are not allowed and result in a runtime error.
A line specification of 0 amounts essentially to no specification.
If n1 number of lines in source code table, the scanner is not called (SY-SUBRC = 2).
If n1 > n2 and n2 > 0, the scanner is not called (SY-SUBRC = 2).

Addition 3
... KEYWORDS FROM itab4
Does not return all statements, only those specified in the key word table itab4.
If the key word table is empty (i.e. it contains 0 lines), all the statements are selected.
The lines of the key word table are treated as a character field.
To select a Native-SQL-statement or a macro definition, you can specify the pseudo key words EXEC_SQL or DEFINE_MACRO. It makes no difference whether the statements EXEC or DEFINE occur as well. Native SQL statements and macro definitions are returned as one statement (of type E or M even if the expansion of a macro definition results in more than one statement.
If the key word table contains a blank line, blank statements are also selected.
Addition 4
... LEVELS INTO itab5
Stores details about each edited source code unit (source code table itab1 itself, expanded include-programs, expanded macro definitions) in the level table itab5.
Specification of a level table makes sense only with the addition WITH INCLUDES.
The level table itab5 must have the structure SLEVEL.
The fields of the structure SLEVEL - and consequently the columns of the level table itab5 have the following meaning:
TYPE
Type of source code unit with the following possible values:
P (Program)
D (Internal DEFINE macro)
R (Macro from table TRMAC)
NAME
Name of source code unit (name of include program, macro name)
DEPTH
Current nesting depth of source code unit (>= 1)
LEVEL
Index of superior (i.e. including or calling) source code unit in the level table (>= 1, if DEPTH >= 2, otherwise 0)
STMNT
Index of superior (i.e. including or calling) statement in the statement table (>= 1, if DEPTH >= 2, otherwise 0)
FROM
Index of first statement of source code unit in the statement table (>= 1)
TO
Index of last statement of source code unit in the statement table (>= 1)
If the source code unit contains include programs or macro calls, the line range [ FROM, TO] in the statement table also covers the statements in subordinate source code units.
Addition 5
... STRUCTURES INTO itab6
Details of the construction of the source text table are given in the structure table itab6.
The structure table itab6 must have the structure SSTRUC.
The fields in SSTRUC (which are also the columns of structure table itab6) have the following meanings:
TYPE
Type of the structure with possible values:
P (Beginning of the source code)
R (Subroutine)
M (Macro, EXEC SQL)
I (Loop)
A (Case distinction)
C (Condition in a case distinction)
J (Goto command)
D (Structured declaration)
E (Event)
S (Follow-on from simple structured statement)
STMNT_TYPE
The statement type of the beginning of the structure. The values are listed in the type pool SCAN in structure SCAN_STRUC_STMNT_TYPE.
KEY_START
Flags whether the start of the structure is described semantically ('X' if there is a special statement, otherwise ' ').
KEY_END
Flags whether the end of the structure is described semantically ('X' if there is a special statement, otherwise blank).
STMNT_FROM
Index of the first statement of the structure in the statement table itab3.
STMNT_TO
Index of the last statement of the structure in the statement table itab3.
Index of the first substructure of the structure in structure table itab6.
STRUC_TO
Index of the last substructure of the structure in structure table itab6.
BACK
Index of the structure in the structure table itab6 that contains the structure as a substructure (0 if the structure is the root structure of a structure tree).
Addition 6
... OVERFLOW INTO c1
The addition is only allowed and required if the token table itab2 has the structure STOKEN or STOKEX.
If a token is too large to be stored in the token table in the field STR, it is placed in the overflow area c1. The offset of the token in the overflow area then lies in the token table in the field OFF1.
Addition 7
... WITH ANALYSIS
Breaks down each token t = a+b(c) according to the logic of the RSYN key word >ANALY into its three components a, b and c.
Offset and length of components a, b and c are stored in the fields LEN1, OFF2, LEN2, OFF3, and LEN3 in the token table. (The offset of OFF1 is always 0 and therefore not required.)
If you specify the addition WITH ANALYSIS, the token table itab2 must have the structure STOKESX, so that the fields LEN1, OFF2, LEN2, OFF3 and LEN3 are available.
If the token table has the structure STOKEX, you must consider the following:
If the whole token exists in the token table, the offset specifications are relative to the token start. If the token is in the overflow area c1, the offset specifications are relative to the start of the overflow area.
Addition 8
... WITH COMMENTS
Returns comments also, with each individual comment representing a token. The system additionally stores entries for each full block of comments in the table itab3, differentiating between comments that occur within statements and those that occur at program level. In itab3, an entry for a comment within a statement always comes before the statement containing the comment.
Example
Look at the following program fragment. The preceding numbers are the indexes of the tokens.
1 * An example *
2 * with scattered comments
6 MOVE
3 * Inserted comment 1
7 X
4 * Inserted comment 2
8 TO
9 Y
5 * Inserted comment 3
SCAN then enters the following values for the components TYPE, FROM and TO (in this order from left to right) into itab3.
'P' 1 2
'S' 3 5
'K' 6 9
If the addition ... WITH COMMENTS is used, the table itab2 must have the line type STOKES or STOKESX.
Addition 9
... WITH INCLUDES
Also breaks down subordinate source code units (included programs, called macros) into tokens.
You should normally combine the addition WITH INCLUDES with the addition LEVELS INTO itab5.
If (at least) one included program does not exist, SY-SUBRC is set to 1 and the relevant INCLUDE statement is flagged in the statement table itab3 by the statement type J (instead of I), but the breakdown process continues. The level table itab5 contains no entry for include-programs that do not exist.
If you combine WITH INCLUDES with WITHOUT TRMAC , TRMAC-Macros are not expanded because the system does not recognize them as subordinate source code units.
When macro calls are expanded, no position specifications are available. The corresponding fields in the token table itab2 and the statement table itab3 are then set to 0.
Addition 10
... WITH TYPE-POOLS
This addition has the same effect as the WITH INCLUDES addition, except that with the former include programs belonging to type groups are broken down into tokens.
Addition 11
.. WITH LIST TOKENIZATION
Tokens of the form (a1, a2, a3) are not returned as tokens but broken down into the elementary components.
Addition 12
... WITHOUT TRMAC
If a statement begins neither with an ABAP/4 key word nor with a DEFINE macro, the system does not check whether this is a TRMAC macro, but assumes an unknown statement. (Unknown statements are flagged in the statement table itab3 with a U in the field TYPE.)
To avoid unnecessary database accesses to the table TRMAC, you should use the addition WITHOUT TRMAC whenever you assume that the source code to be scanned contains unknown statements. Unknown statements are particularly likely to occur if you use the addition FROM n1, because the scanner does not start at the beginning of the source code, but from a specified point.
If you use WITHOUT TRMAC with WITH INCLUDES, TRMAC macros are not expanded because the system does not recognize them as subordinate source code units.
Addition 13
... PROGRAM FROM c2
Addition 14
... INCLUDE INTO c3
Addition 15
... MESSAGE INTO c4
Addition 16
... WORD INTO c5
Addition 17
... LINE INTO n3
Addition 18
... OFFSET INTO n4
The above additions have the same meaning as those for the
SYNTAX-CHECK: statement: c2 is an input field for a program name to be assigned to the source code, while the fields c3, c4, c5, n3 and n4 are output fields in case an error occurs.
To be able to analyze errors without modifying programs, use the additions INCLUDE, MESSAGE, WORD, LINE and OFFSET. These provide information about the errors which have occurred.
Variant 2
SCAN AND CHECK ABAP-SOURCE itab1 ...RESULT INTO itab2.
Parts marked with " ..." are interchangeable
Extras:
1. ... PROGRAM FROM c1 2. ... INCLUDE INTO c2
3. ... MESSAGE INTO c3
4. ... WORD INTO c4
5. ... LINE INTO n1
6. ... OFFSET INTO n2
The syntax of the program in table itab1 is checked. During the check, all of the information from the program, such as statement structures, statements, tokens, data objects, types and do on are placed into the result field. This field must have the type SYSCH_RESULT, which is defined in type group SYSCH. You must therefore declare type group SYSCH in your ABAP-program using a TYPE-POOLS statement.
&ABAP_ADDITION _1&
... PROGRAM FROM c1
&ABAP_ADDITION _2&
... INCLUDE INTO c1
&ABAP_ADDITION _3&
... MESSAGE INTO c3
&ABAP_ADDITION _4&
... WORD INTO c4
&ABAP_ADDITION _5&
... LINE INTO n1
&ABAP_ADDITION _6&
... OFFSET INTO n2
The above additions have the same effect as the corresponding additions in the statement SYNTAX-CHECK: c1 is an input field for a program name to be assigned to the source code, the fields c2, c3, c4, n1 and n2 are output fields, used when errors occur.
To enable you to analyze errors without having to modify the program, you should specify the INCLUDE, MESSAGE, WORD, LINE and OFFSET additions for the information about the error that occurred.
Reward if usefull

What is the use P type variable in ABAP?

ex:
data <variable name > type p decimals 2.
here what is the use of declaring it to p type.
what is the difference between p type and float type.

Hi,
using packed variable we can decide the length of number and number of decimals we want in o/p which is not possible with other types
Packed numbers - type P
Type P data allows digits after the decimal point. The number of decimal places is generic, and is determined in the program. The value range of type P data depends on its size and the number of digits after the decimal point. The valid size can be any value from 1 to 16 bytes. Two decimal digits are packed into one byte, while the last byte contains one digit and the sign. Up to 14 digits are allowed after the decimal point. The initial value is zero. When working with type P data, it is a good idea to set the program attribute Fixed point arithmetic.Otherwise, type P numbers are treated as integers.
You can use type P data for such values as distances, weights, amounts of money, and so on.
Floating point numbers - type F
The value range of type F numbers is 1x10*-307 to 1x10*308 for positive and negative numbers, including 0 (zero). The accuracy range is approximately 15 decimals, depending on the floating point arithmetic of the hardware platform. Since type F data is internally converted to a binary system, rounding errors can occur. Although the ABAP processor tries to minimize these effects, you should not use type F data if high accuracy is required. Instead, use type P data.
You use type F fields when you need to cope with very large value ranges and rounding errors are not critical.
Using I and F fields for calculations is quicker than using P fields. Arithmetic operations using I and F fields are very similar to the actual machine code operations, while P fields require more support from the software. Nevertheless, you have to use type P data to meet accuracy or value range requirements.

What is the use of internal document number in excise invoice

Similar Messages

Maybe you are looking for